Re: conchuela timeouts since 2021-10-09 system upgrade

Andrey Borodin <x4mmm@yandex-team.ru>

From: Andrey Borodin <x4mmm@yandex-team.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Noah Misch <noah@leadboat.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>, Michael Paquier <michael@paquier.xyz>, Peter Geoghegan <pg@bowt.ie>, Andres Freund <andres@anarazel.de>
Date: 2021-10-25T08:30:32Z
Lists: 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 can share VM state if it's of any help.

Best regards, Andrey Borodin.


Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Improve contrib/amcheck's tests for CREATE INDEX CONCURRENTLY.

  2. Fix minor memory leaks in pg_dump.

  3. Avoid race in RelationBuildDesc() affecting CREATE INDEX CONCURRENTLY.

  4. Fix CREATE INDEX CONCURRENTLY for the newest prepared transactions.

  5. Add -w back to the flags for pg_ctl (re)start in PostgresNode

  6. Fix CREATE INDEX CONCURRENTLY for simultaneous prepared transactions.