Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kNLwF-0006HO-81 for pgsql-bugs@arkaria.postgresql.org; Tue, 29 Sep 2020 20:09:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kNLwE-00066O-4C for pgsql-bugs@arkaria.postgresql.org; Tue, 29 Sep 2020 20:09:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kNLwD-00066G-Ur for pgsql-bugs@lists.postgresql.org; Tue, 29 Sep 2020 20:09:25 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kNLwA-0002WF-OF for pgsql-bugs@lists.postgresql.org; Tue, 29 Sep 2020 20:09:24 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 08TK9KLC718214; Tue, 29 Sep 2020 16:09:20 -0400 From: Tom Lane To: henry.hinze@googlemail.com cc: 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: <16643-eaadeb2a1a58d28c@postgresql.org> References: <16643-eaadeb2a1a58d28c@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Tue, 29 Sep 2020 19:46:59 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <718212.1601410160.1@sss.pgh.pa.us> Date: Tue, 29 Sep 2020 16:09:20 -0400 Message-ID: <718213.1601410160@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > The following setup of logical replication for one table works nicely with > PG 12.4. In PG 13.0 the initial startup never finishes. Instead it starts > over and over again. It kinda looks like something is timing out before it's managed to catch up with the (rather large) initial state of table t. What non-default replication settings are you using? regards, tom lane