Horton
Menu

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

Peter Geoghegan <pg@bowt.ie>

View thread
From: Peter Geoghegan <pg@bowt.ie>
To: Noah Misch <noah@leadboat.com>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>, Michael Paquier <michael@paquier.xyz>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2021-08-24T06:38:51Z
Lists: pgsql-bugs 
On Mon, Aug 23, 2021 at 10:37 PM Noah Misch <noah@leadboat.com> wrote:
> > There was a race condition in deterministic 2PC test. Fixed with synchronisation points.
> > PFA patches that work on my machines.
> > I'm going to start fixing review notes if it will not break until tomorrow.
>
> That is great news.

+1. Great detective work.


-- 
Peter Geoghegan

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.