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 1no6JB-0002Ww-Bk for pgsql-bugs@arkaria.postgresql.org; Mon, 09 May 2022 16:32:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1no6JA-0000nL-5W for pgsql-bugs@arkaria.postgresql.org; Mon, 09 May 2022 16:32:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1no6J9-0000nC-T8 for pgsql-bugs@lists.postgresql.org; Mon, 09 May 2022 16:32:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1no6J7-00069Y-U4 for pgsql-bugs@lists.postgresql.org; Mon, 09 May 2022 16:32:27 +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 249GWNkI3816956; Mon, 9 May 2022 12:32:23 -0400 From: Tom Lane To: Maxim Boguk cc: spastrilov@gmail.com, PostgreSQL mailing lists Subject: Re: BUG #17478: Missing documents in the index after CREATE INDEX CONCURRENTLY (but existing in the table) In-reply-to: References: <17478-c422e68d010b951d@postgresql.org> Comments: In-reply-to Maxim Boguk message dated "Mon, 09 May 2022 18:24:22 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <3816954.1652113943.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 09 May 2022 12:32:23 -0400 Message-ID: <3816955.1652113943@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Maxim Boguk writes: > On Mon, May 9, 2022 at 5:58 PM PG Bug reporting form > wrote: >> We=E2=80=99re observing a strange bug, according to me. We=E2=80=99ve g= ot native logical >> replication where the master host is running on PostgreSQL 13.3 and the >> logical replica host is running on PostgreSQL 14.1. And the problem is: >> when we start to reindex concurrently the primary key of an 800M heavil= y >> inserted/updated(on the master)table on the logical replica database, >> several documents that have been inserted and existing in the master >> database during the index rebuild on the replica, are missing from the >> index >> structure on the replica host. > Please try to upgrade your slave to 14.2 where this problem was fixed (a= t > least it fixed the same issue for me). 13.6 might do as well, and would be a lot closer to a drop-in upgrade. The 13.5 and 13.6 release notes both mention problems with REINDEX CONCURRENTLY. Given the existence of those fixed bugs, nobody is likely to look too closely at this report unless you can still reproduce it on a current minor release. regards, tom lane