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

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Date: 2021-07-29 14:21:44
Message-ID: ABABD793-1438-445B-879E-457499C2FC11@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> 29 июля 2021 г., в 17:30, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> написал(а):
>
> Searching further.

Currently CIC test breaks indexes even without 2PC. How is it supposed to work if vxid stays vxid through GetLockConflicts()\WaitForLockersMultiple() barrier and then suddenly converts to xid and commits before index validated?

Best regards, Andrey Borodin.

Attachment Content-Type Size
v7-0001-Do-not-use-Prepared-transactions-in-CIC-test.patch application/octet-stream 6.5 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2021-07-29 21:19:24 Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
Previous Message Andrey Borodin 2021-07-29 12:30:56 Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data