Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data - Mailing list pgsql-bugs

From Andrey Borodin
Subject Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Date
Msg-id 85D32B53-FB25-4F2F-A253-0D7B26F72881@yandex-team.ru
Whole thread Raw
In response to Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-bugs

> 31 июля 2021 г., в 13:51, Peter Geoghegan <pg@bowt.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.


pgsql-bugs by date:

Previous
From: Dave Cramer
Date:
Subject: Re: pg_stat warnings keep on printing in postgres log
Next
From: PG Bug reporting form
Date:
Subject: BUG #17137: Bug with datatypes definition in CTE