Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stefan Froehlich <postgresql(at)froehlich(dot)priv(dot)at>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault
Date: 2022-11-06 14:13:08
Message-ID: 3007238.1667743988@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Stefan Froehlich <postgresql(at)froehlich(dot)priv(dot)at> writes:
> I followed the suggestion to trace down the faulty record, found and
> fixed it. Now I can access that record again, but if I try to dump
> the table I get:
> | 2022-11-06 11:52:36.367 CET [2098-35] LOG: server process (PID 2964738) was terminated by signal 11: Segmentation fault

> Whatever was "done" does not prevent the problem from being
> reproducible. I tried to track down this faulty record as well, but
> binary proves difficult with 25*10^6 rows if the server crashes and
> rebuilds after each try.
> Is there any reasonable way to proceed from here?

contrib/amcheck might help to identify the faulty data (at this
point there's reason to fear multiple corruptions ...). If
you're running v14 or v15 there's a frontend for that called
pg_amcheck.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Erik Wienhold 2022-11-06 14:23:19 Re: an difficult SQL
Previous Message Rafal Pietrak 2022-11-06 12:48:29 Re: an difficult SQL