From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stefan Froehlich <postgresql@froehlich.priv.at>
Cc: pgsql-general@postgresql.org
Subject: Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault
Date: Sun, 06 Nov 2022 09:13:08 -0500
Message-ID: <3007238.1667743988@sss.pgh.pa.us> (raw)
In-Reply-To: <20221106111820.GA26442@static.231.150.9.176.clients.your-server.de>
References: <20221106111820.GA26442@static.231.150.9.176.clients.your-server.de>
Stefan Froehlich <postgresql@froehlich.priv.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
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, postgresql@froehlich.priv.at
Subject: Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault
In-Reply-To: <3007238.1667743988@sss.pgh.pa.us>
References: <20221106111820.GA26442@static.231.150.9.176.clients.your-server.de> <3007238.1667743988@sss.pgh.pa.us>
* 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