pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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:48:32 -0500
Message-ID: <3010779.1667746112@sss.pgh.pa.us> (raw)
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>

Stefan Froehlich <postgresql@froehlich.priv.at> writes:
> 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

Oh ... up through v13, amcheck lacks any functions to check heaps,
only indexes, so I guess it won't help you much.  You could try
reindexing, but if pg_dump is failing that's a good sign you have
heap corruption not (or at least not only) index corruption.

Another idea is to try using contrib/pageinspect to examine each
page of the table.  Its output is just gobbledegook to most people,
but there's a good chance it'd fail visibly on the corrupted page(s).

Also, please read
https://wiki.postgresql.org/wiki/Corruption
if you didn't already.

			regards, tom lane





view thread (13+ messages)  latest in thread

Message-ID: <3010779.1667746112@sss.pgh.pa.us>
Permalink:  ../3010779.1667746112@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3010779.1667746112@sss.pgh.pa.us

 · 

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: 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: <3010779.1667746112@sss.pgh.pa.us>
  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> <3010779.1667746112@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