Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process - Mailing list pgsql-admin

From Laurenz Albe
Subject Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
Date
Msg-id 6e6406c18726b29b5264c10dc548276dcd0173c0.camel@cybertec.at
Whole thread Raw
In response to Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process  (Veerendra Pulapa <veerendra.pulapa@ashnik.com>)
Responses Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
List pgsql-admin
On Mon, 2024-06-17 at 18:30 +0530, Veerendra Pulapa wrote:
> LOG:  startup process (PID 21704) was terminated by signal 11: Segmentation fault

If you want any support for that, you need to collect a core dump and
generate a stack trace.  Make sure that you have the debugging symbols installed.

Also, we'd need to see the log messages *before* the lines you show.  Everything
since the start of the server.

A segmentation fault is caused by a software bug.  Since it happens during
recovery, perhaps the WAL that is being replayed is corrupted and makes
PostgreSQL fail.

My recommendation is to restore your last good backup.

Yours,
Laurenz Albe



pgsql-admin by date:

Previous
From: Veerendra Pulapa
Date:
Subject: Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
Next
From: Tom Lane
Date:
Subject: Re: Custom ordering operator for type xid