Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r41cb-00741u-LP for pgsql-bugs@arkaria.postgresql.org; Fri, 17 Nov 2023 16:23:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r41cY-00EiXR-BL for pgsql-bugs@arkaria.postgresql.org; Fri, 17 Nov 2023 16:23:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r41cY-00EiXJ-1I for pgsql-bugs@lists.postgresql.org; Fri, 17 Nov 2023 16:23:06 +0000 Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r41cV-0062Un-3P for pgsql-bugs@lists.postgresql.org; Fri, 17 Nov 2023 16:23:04 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com; s=20170201; h=In-Reply-To:Content-Type:MIME-Version:References:Reply-To: Message-ID:Subject:Cc:To:Sender:From:Date:Content-Transfer-Encoding: Content-ID:Content-Description; bh=Oalunim/xdDNb3/83SUfQFMFDXb9CrCU32HPjboi/0k=; b=rp8PrcjgGHCIQIdaTUp9N6nc3c vt976ItXjKbc+6kbQbQEHLH/YejaDwk201JPgY5R8CA1NFrUKbAYO5BEIFux3MPpoFvcbP/KLVcVX a04sy6ewb5Tb3KHzN+EvX16seyOiUaKkz+TZLe65buDyJ5OZlQCYBxUZSpcsBVvnv9Bc=; Received: from depesz by depesz.com with local (Exim 4.96) (envelope-from ) id 1r41cQ-007jMf-0m; Fri, 17 Nov 2023 17:22:58 +0100 Date: Fri, 17 Nov 2023 17:22:58 +0100 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: Tomas Vondra Cc: "Hayato Kuroda (Fujitsu)" , Amit Kapila , Kyotaro Horiguchi , "pgsql-bugs@lists.postgresql.org" Subject: Re: Logical replication is missing block of rows when sending initial sync? Message-ID: Reply-To: depesz@depesz.com References: <2a638962-7a62-abd6-d9a4-3c322ec2a06d@enterprisedb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Nov 17, 2023 at 03:40:35PM +0100, Tomas Vondra wrote: > On 11/15/23 02:41, Hayato Kuroda (Fujitsu) wrote: > > Dear Tomas, Depesz, > > > >> > >>> I'll try reproducing this locally over the weekend. Should I use the > >>> test_1030.sh script that you shared a week ago, or do I need to do > >>> something more? > >> > >> That question is probably not to me, but to Hayato Kuroda > > > > Just FYI - As I posted, this script could not reproduce the issue. We may use the same table definition > > but I have not tried yet. I will let you know if I succeeded to reproduce. > > > > FYI I think I've reproduced the issue (with a different script), I've > started a thread on pgsql-hackers: > > https://www.postgresql.org/message-id/de52b282-1166-1180-45a2-8d8917ca74c6%40enterprisedb.com > > Obviously, I can't be sure it's exactly the same issue, but the symptoms > seem to match what Depesz reported (gaps in data etc.). I don't know > what the root cause is, or fix. But there's more info (and scripts) in > the hackers thread. Thanks a lot. Much appreciated. It will be over for us with the upgrade soon, but it's good to know that there might be one less bug in pg thanks to this :) Best regards, depesz