pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: mircea@reva.tech
Subject: BUG #16094: Database entering recovery mode
Date: Mon, 04 Nov 2019 14:50:45 +0000
Message-ID: <16094-8fb7061e5370fb00@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16094
Logged by:          Mircea Pirv
Email address:      mircea@reva.tech
PostgreSQL version: 12.0
Operating system:   OSX
Description:        

Hello, 

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.
Our setup has replication enabled, with a replication slot, and using a
replication subscription. On our development machines replication is setup
to use the same machine.
The problem is, that with replication enabled, changing a column value using
an update statement, causes the database to enter recovery mode.
This happens only when replication is enabled.
We could not find any pattern, like what kind of columns might be the
culprit. It happens with all kinds of columns, regardless of the fact that
we have constraints, triggers, defaults on the columns. With some columns it
happens randomly, with some it happens all the time.

In the logs the only error we see, is a segmentation fault, when replication
tries to run.
We tried with both a local server, and a dockerized version (12.0).

It only reproduces in 12.0. 10.6 and 11.5 do not have this problem, we could
not reproduce it.

Any ideas on what may have changed in 12.0 to cause this behavior ?

Thanks,
Mircea



view thread (5+ messages)  latest in thread

Message-ID: <16094-8fb7061e5370fb00@postgresql.org>
Permalink:  ../16094-8fb7061e5370fb00@postgresql.org/
Also on:    postgresql.org/message-id/16094-8fb7061e5370fb00@postgresql.org

 · 

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: noreply@postgresql.org, mircea@reva.tech
  Subject: Re: BUG #16094: Database entering recovery mode
  In-Reply-To: <16094-8fb7061e5370fb00@postgresql.org>
  References: <16094-8fb7061e5370fb00@postgresql.org>

* 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