| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Veerendra Pulapa <veerendra(dot)pulapa(at)ashnik(dot)com>, Achilleas Mantzios <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process |
| Date: | 2024-06-17 14:39:41 |
| Message-ID: | 6e6406c18726b29b5264c10dc548276dcd0173c0.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-06-17 15:03:58 | Re: Custom ordering operator for type xid |
| Previous Message | Veerendra Pulapa | 2024-06-17 13:00:44 | Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process |