Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Date: 2021-08-06 18:03:18
Message-ID: 85D32B53-FB25-4F2F-A253-0D7B26F72881@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> 31 июля 2021 г., в 13:51, Peter Geoghegan <pg(at)bowt(dot)ie> написал(а):
>
> maybe use rr for this?

rr helps to explain why something happened.
But how to get why something did not happen?
During GetLockConflicts() proclocks SHMQueue do not include locks of concurrently running xid within PrepareTransaction() [seems like it's with PostPrepare_locks(), but I'm not sure].
The problem is reproducible within 1 second by the script leading to amcheck-detected corruption.

I'd appreciate one more hint...
Thanks!

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-08-06 18:12:28 BUG #17137: Bug with datatypes definition in CTE
Previous Message Dave Cramer 2021-08-06 12:48:24 Re: pg_stat warnings keep on printing in postgres log