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-02 12:45:54
Message-ID: 9B31541B-4750-4058-90DC-58FF975F37B3@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?
Thanks, Peter!
I'll give it a try.

Currently I observe that during PrepareTransaction() there might be a moment when the transaction is not reported by GetLockConflicts() with relevant lock.

I observe that PrepareTransaction() for violating xid is somewhere between
CallXactCallbacks(XACT_EVENT_PREPARE);
and
PostPrepare_PgStat();

And GetLockConflicts() fails to detect this transaction.

Thanks!

Best regards, Andrey Borodin.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2021-08-02 13:08:35 Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
Previous Message Wojciech Strzalka 2021-08-02 10:57:17 Re: psql doesn't show tables duplicated in multiple schemas