Re: conchuela timeouts since 2021-10-09 system upgrade - Mailing list pgsql-bugs

From Andrey Borodin
Subject Re: conchuela timeouts since 2021-10-09 system upgrade
Date
Msg-id B5CC4C8F-1B73-4359-AF68-26A08A17BCD1@yandex-team.ru
Whole thread Raw
In response to Re: conchuela timeouts since 2021-10-09 system upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: conchuela timeouts since 2021-10-09 system upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs

> 25 окт. 2021 г., в 02:53, Tom Lane <tgl@sss.pgh.pa.us> написал(а):
>
> I can poke into it tomorrow.

FWIW it's easy to make the issue reproduce faster with following diff

diff --git a/contrib/amcheck/t/003_cic_2pc.pl b/contrib/amcheck/t/003_cic_2pc.pl
index f4255c1fb8..0d68c53387 100644
--- a/contrib/amcheck/t/003_cic_2pc.pl
+++ b/contrib/amcheck/t/003_cic_2pc.pl
@@ -141,7 +141,7 @@ $node->safe_psql('postgres', q(REINDEX TABLE tbl;));
 my $pgbench_out   = '';
 my $pgbench_timer = IPC::Run::timeout(180);
 my $pgbench_h     = $node->background_pgbench(
-       '--no-vacuum --client=1 --transactions=100',
+       '--no-vacuum --client=1 --transactions=1',
        {
                '002_pgbench_concurrent_cic' => q(
                        DROP INDEX CONCURRENTLY idx;

I.e. if pgbench exits earlier than we call finish() it always hangs. I observe reproduction on my Drogonfly VM and I
canshare VM state if it's of any help. 

Best regards, Andrey Borodin.


pgsql-bugs by date:

Previous
From: Marek Läll
Date:
Subject: Re: BUG #17240: at time zone ... ; wrong result
Next
From: Andrew Gierth
Date:
Subject: Re: BUG #17245: Index corruption involving deduplicated entries