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 1qytCM-00BpRR-VL for pgsql-bugs@arkaria.postgresql.org; Fri, 03 Nov 2023 12:22:50 +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 1qytCL-000QXx-1f for pgsql-bugs@arkaria.postgresql.org; Fri, 03 Nov 2023 12:22:49 +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 1qytCK-000QXm-PT for pgsql-bugs@lists.postgresql.org; Fri, 03 Nov 2023 12:22:48 +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 1qytCI-003lI5-ED for pgsql-bugs@lists.postgresql.org; Fri, 03 Nov 2023 12:22:47 +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=j6Z5KVhgvcBIYwKPtsEL583vQCZOL8UjGLWrZ8mfUVU=; b=iZgKLhPkux/+LMy5k2JA5F/8OG SFx77BfRdqN5rTTHVz0ePxJNAoIhvg5IuS5tH8ac6HB9r7clMd0CRbVSdBg/29o3wl4+7MOJnkw1w ZfpAxK8zsCcay7YsDLd0DHwSw8NJvmTjjw3BjmW1bfmb+mChmucK0kC2TZIz+a+yl+9A=; Received: from depesz by depesz.com with local (Exim 4.94.2) (envelope-from ) id 1qytCE-009CXz-F7; Fri, 03 Nov 2023 13:22:42 +0100 Date: Fri, 3 Nov 2023 13:22:42 +0100 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: Tomas Vondra Cc: Amit Kapila , Kyotaro Horiguchi , kuroda.hayato@fujitsu.com, 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: <20231102.101713.170587046871054404.horikyota.ntt@gmail.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 03, 2023 at 01:20:22PM +0100, Tomas Vondra wrote: > I think it'd be interesting to know: > > 1) Commit LSN for the missing rows (for the xmin). > > 2) Are the other changes for these transactions that *got* replicated > correctly? How would I know? > 3) LSNs used for the tablesync slot, catchup etc. I believe those are in > the server log. I will provide more logs on the next problem. Best regards, depesz