From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Henry Hinze <henry.hinze@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop
Date: Thu, 1 Oct 2020 19:24:17 +0200
Message-ID: <61e8b017-ad50-cedd-c85e-4e6c07322ac4@2ndquadrant.com> (raw)
In-Reply-To: <912614.1601502758@sss.pgh.pa.us>
References: <20200930214216.GA5296@alvherre.pgsql>
<912614.1601502758@sss.pgh.pa.us>
On 2020-09-30 23:52, Tom Lane wrote:
> One thing I noticed while trying to trace this down is that while the
> initial table sync is happening, we have *both* a regular
> walsender/walreceiver pair and a "sync" pair, eg
>
> postgres 905650 0.0 0.0 186052 11888 ? Ss 17:12 0:00 postgres: logical replication worker for subscription 16398
> postgres 905651 50.1 0.0 173704 13496 ? Ss 17:12 0:09 postgres: walsender postgres [local] idle
> postgres 905652 104 0.4 186832 148608 ? Rs 17:12 0:19 postgres: logical replication worker for subscription 16398 sync 16393
> postgres 905653 12.2 0.0 174380 15524 ? Ss 17:12 0:02 postgres: walsender postgres [local] COPY
That's normal. You could also have even more if tables are syncing in
parallel.
--
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, alvherre@alvh.no-ip.org, henry.hinze@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop
In-Reply-To: <61e8b017-ad50-cedd-c85e-4e6c07322ac4@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