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 1qiVtO-006eBx-Mh for pgsql-bugs@arkaria.postgresql.org; Tue, 19 Sep 2023 08:15:34 +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 1qiVtN-007jKs-A2 for pgsql-bugs@arkaria.postgresql.org; Tue, 19 Sep 2023 08:15:33 +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 1qiVtN-007jKO-0S for pgsql-bugs@lists.postgresql.org; Tue, 19 Sep 2023 08:15:33 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qiVtK-005PJj-1M for pgsql-bugs@lists.postgresql.org; Tue, 19 Sep 2023 08:15:31 +0000 Received: from mail.postgrespro.ru (webmail.mstn.postgrespro.ru [192.168.2.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: a.pyhalov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 6926CE20E71; Tue, 19 Sep 2023 11:15:29 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1695111329; bh=QajUa0b5YivquCvvXA32Z5g97CFEOkLuaLdYOiPwzNE=; h=Date:From:To:Cc:Subject:In-Reply-To:References:User-Agent: Message-ID:From; b=Ax2riNkvHg5AhvCeDpOlLYnxK5VkDGYphRV/p9oULmFlTpxHvcmZfMeauVNWMP9PN EFPpBwfUejX+F2zPjrLNoLk596YwQlQEBk4fmEi003YyT1ydE50pgvJcx5sIr/KM4I caOGbbeX4WzCEDr/h6QWq5KTyRyIKKQMHCgQ3U8anI9GRCUbR5Xa4xJZCkoDXfTQvF w9tpHXWgg1Yxp4hQT7vDBoxBdjTQKbAEmG48SuFOtHvU+Qjd2fvCgwbsx++6fDJrms WajvVRrYUkdtH7YaCK3h2Of+L0xHdIzbPblwn1oHZLkA2FNAY8cwkcvZ1zXoGvHRIA UVydiXAFWh2YQ== MIME-Version: 1.0 Date: Tue, 19 Sep 2023 11:15:29 +0300 From: Alexander Pyhalov To: Daniel Gustafsson Cc: Alexander Lakhin , Masahiko Sawada , bowenshi , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17695: Failed Assert in logical replication snapbuild. In-Reply-To: <9C8BF118-5869-49B0-81D7-BA072AD8E88E@yesql.se> References: <17695-6be9277c9295985f@postgresql.org> <7e4d4a80-3e3c-231f-f886-6cada2aa582b@gmail.com> <102cb85d-2205-c8ec-ac37-797c03e025e1@gmail.com> <9C8BF118-5869-49B0-81D7-BA072AD8E88E@yesql.se> User-Agent: Roundcube Webmail/1.4.11 Message-ID: <09bebdfe9d4a2c6155379442f0771bfe@postgrespro.ru> X-Sender: a.pyhalov@postgrespro.ru Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Daniel Gustafsson писал 2023-07-04 18:43: >> On 23 May 2023, at 13:00, Alexander Lakhin >> wrote: >> >> 22.05.2023 03:56, Masahiko Sawada wrote: >>> On Thu, May 18, 2023 at 11:00 PM Alexander Lakhin >>> wrote: >>> >>>> I can easily (without gdb and sleep()) reproduce the issue on master >>>> with >>>> the following script: >>>> ... >>> Thank you for sharing the script. But it seems not stable as I could >>> not reproduce the issue in my environment. I think we need a stable >>> reproducer so that we can include it in core regression tests. Or it >>> may be okay not to include it if we could not find a convenient way >>> and the fix is trivial. >> >> I've came to the minimal reproducer: > > Thanks for the reproducer, I was able to reproduce this in HEAD and > v16. > >> It's hardly suitable for the regression test, but it clearly >> demonstrates the >> issue without using gdb. With the fix from [1] applied, I've got no >> failures, >> even with numclients=100, for 10 runs. >> >> I also think, that the fix is simple enough to be committed without a >> complicated/resource-intensive regression test. > > I'm not convinced we need a regression test for this as it would be > very > expensive and potentially brittle for older/slower buildfarm members > while > giving few gains. > > I've applied this to HEAD and backpatched it to v16. > Hi. It seems we've managed to get this issue on 14.8. Is there any reason why it wasn't applied to earlier versions? -- Best regards, Alexander Pyhalov, Postgres Professional