From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Henry Hinze <henry.hinze@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org, Alvaro Herrera <alvherre@2ndquadrant.com>
Subject: Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop
Date: Thu, 1 Oct 2020 19:22:44 +0200
Message-ID: <e7521db4-119f-b256-f338-a35d80d50fb4@2ndquadrant.com> (raw)
In-Reply-To: <911656.1601501524@sss.pgh.pa.us>
References: <16643-eaadeb2a1a58d28c@postgresql.org>
<718213.1601410160@sss.pgh.pa.us>
<CAJs-y_-6c+OH=3ofq7SsANZ7JOpy-yUW37WmAD6XhFi3_csN=w@mail.gmail.com>
<CAJs-y__J696sux=7--UFSYxyeZ6aLJbdKdhq_YZjgCuxmHhbgw@mail.gmail.com>
<911656.1601501524@sss.pgh.pa.us>
On 2020-09-30 23:32, Tom Lane wrote:
> The question that this raises is how the heck did that get past
> our test suites? It seems like the error should have been obvious
> to even the most minimal testing.
What's the difference between this case and what the test suite is
testing? Is it that it replicates between two databases on the same
instance?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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 using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, henry.hinze@gmail.com, alvherre@2ndquadrant.com
Subject: Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop
In-Reply-To: <e7521db4-119f-b256-f338-a35d80d50fb4@2ndquadrant.com>
* 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