pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: mircea@reva.tech
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16094: Database entering recovery mode
Date: Mon, 04 Nov 2019 10:03:45 -0500
Message-ID: <6649.1572879825@sss.pgh.pa.us> (raw)
In-Reply-To: <16094-8fb7061e5370fb00@postgresql.org>
References: <16094-8fb7061e5370fb00@postgresql.org>

PG Bug reporting form <noreply@postgresql.org> writes:
> We've updated our database from 10.6 to 12.0 recently and we keep
> encountering an error which says that the database is entering recovery
> mode.
> ...
> In the logs the only error we see, is a segmentation fault, when replication
> tries to run.

It should be possible to collect a stack trace for the segfault,
which would greatly assist debugging this.  Please see

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

			regards, tom lane





view thread (5+ messages)  latest in thread

Message-ID: <6649.1572879825@sss.pgh.pa.us>
Permalink:  ../6649.1572879825@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6649.1572879825@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-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mircea@reva.tech
  Subject: Re: BUG #16094: Database entering recovery mode
  In-Reply-To: <6649.1572879825@sss.pgh.pa.us>
  References: <16094-8fb7061e5370fb00@postgresql.org> <6649.1572879825@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