pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stefan Froehlich <postgresql@froehlich.priv.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@postgresql.org
Subject: Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault
Date: Sun, 6 Nov 2022 15:35:44 +0100
Message-ID: <20221106143544.GA4940@static.231.150.9.176.clients.your-server.de> (raw)
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>

On Sun, Nov 06, 2022 at 09:13:08AM -0500, Tom Lane wrote:
> > | 2022-11-06 11:52:36.367 CET [2098-35] LOG:  server process (PID 2964738) was terminated by signal 11: Segmentation fault
 
> 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.

I am using v13, but well:

| # create extension amcheck;
| # select oid, relname from pg_class where relname ='faultytablename_pkey';
| [returns oid 537203]
| # select bt_index_check(537203, true);
| server closed the connection unexpectedly
|         This probably means the server terminated abnormally
|         before or while processing the request.
| The connection to the server was lost. Attempting reset: Failed.

This seems to be quite fucked up ("how" would be a good question,
too, but for the moment priority is to work around the problem).

If I have to delete 1k records in this table, I'll do and survive,
but first I have to find out which ones.

Bye,
Stefan





view thread (13+ messages)  latest in thread

Message-ID: <20221106143544.GA4940@static.231.150.9.176.clients.your-server.de>
Permalink:  ../20221106143544.GA4940@static.231.150.9.176.clients.your-server.de/
Also on:    postgresql.org/message-id/20221106143544.GA4940@static.231.150.9.176.clients.your-server.de

 · 

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 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: postgresql@froehlich.priv.at, tgl@sss.pgh.pa.us
  Subject: Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault
  In-Reply-To: <20221106143544.GA4940@static.231.150.9.176.clients.your-server.de>
  References: <20221106111820.GA26442@static.231.150.9.176.clients.your-server.de> <3007238.1667743988@sss.pgh.pa.us> <20221106143544.GA4940@static.231.150.9.176.clients.your-server.de>

* 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