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@lists.postgresql.org
Subject: Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault
Date: Mon, 07 Nov 2022 09:02:26 -0500
Message-ID: <3192952.1667829746@sss.pgh.pa.us> (raw)
In-Reply-To: <20221107134710.GA7369@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>
	<3010779.1667746112@sss.pgh.pa.us>
	<20221107101716.GA20949@static.231.150.9.176.clients.your-server.de>
	<0fb331d6fa4743a89070e092c62020ffee3020a5.camel@cybertec.at>
	<54262965-310e-327b-d7be-ef3e6a0ed2eb@gmail.com>
	<20221107134710.GA7369@static.231.150.9.176.clients.your-server.de>

Stefan Froehlich <postgresql@froehlich.priv.at> writes:
> On Mon, Nov 07, 2022 at 08:17:10AM -0500, Mladen Gogala wrote:
>> On 11/7/22 06:19, Laurenz Albe wrote:
>>> Don't continue to work with that cluster even if everything seems OK now.
>>> "pg_dumpall" and restore to a new cluster on good hardware.
 
>> Why would that be necessary if the original machine works well now?

> I can understand the idea not to trust hardware anymore once a (not
> clearly identified) problem occured.

> In this case new hardware would - for reasons beyond the scope of
> this list - not be any more or less trustworthy than the existing
> one and thus (IMO) not make any difference.

Whether you want to continue to trust the hardware or not is your
call.  It'd still be recommendable to pg_dumpall and restore into
a freshly-initdb'd cluster, because otherwise you can't be real
sure that you identified and cleared all the data corruption.

			regards, tom lane





view thread (13+ messages)  latest in thread

Message-ID: <3192952.1667829746@sss.pgh.pa.us>
Permalink:  ../3192952.1667829746@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3192952.1667829746@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: <3192952.1667829746@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> <20221107101716.GA20949@static.231.150.9.176.clients.your-server.de> <0fb331d6fa4743a89070e092c62020ffee3020a5.camel@cybertec.at> <54262965-310e-327b-d7be-ef3e6a0ed2eb@gmail.com> <20221107134710.GA7369@static.231.150.9.176.clients.your-server.de> <3192952.1667829746@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