pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Laurenz Albe <laurenz.albe@cybertec.at>
To: veerendra.pulapa@ashnik.com
To: pgsql-admin@postgresql.org
Subject: Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
Date: Mon, 01 Jul 2024 14:40:50 +0200
Message-ID: <f70ccfb62e91ca4a4a195365d89a67ecdbb41bbb.camel@cybertec.at> (raw)

Veerendra Pulapa wrote:
> I am reaching out to discuss an issue we recently encountered with our PostgreSQL
> setup, where a bug triggered on our standby servers before it affected the master.
> I am seeking insights into whether the resource differences between our servers
> could have played a role in this sequence of events.
>
> Issue Overview:
>
> We observed a signal 11 (segmentation fault) error that first appeared on our
> standby servers and subsequently affected the master server.

Please don't hijack another thread, start your own.

You should tell us the exact PostgreSQL version and operating system.
Also, tell us exactly what you did to trigger the problem.
Collect a core dump and get a stack trace (you need debugging symbols):
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

Yours,
Laurenz Albe

view thread (16+ messages)

Message-ID: <f70ccfb62e91ca4a4a195365d89a67ecdbb41bbb.camel@cybertec.at>
Permalink:  ../f70ccfb62e91ca4a4a195365d89a67ecdbb41bbb.camel@cybertec.at/
Also on:    postgresql.org/message-id/f70ccfb62e91ca4a4a195365d89a67ecdbb41bbb.camel@cybertec.at

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: laurenz.albe@cybertec.at, veerendra.pulapa@ashnik.com
  Subject: Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
  In-Reply-To: <f70ccfb62e91ca4a4a195365d89a67ecdbb41bbb.camel@cybertec.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox