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

From: Noah Misch <noah(at)leadboat(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
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-23 22:30:21
Message-ID: 20210723223021.GA1354601@gust.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jul 23, 2021 at 09:33:18PM +0500, Andrey Borodin wrote:
> > 21 июля 2021 г., в 22:55, Noah Misch <noah(at)leadboat(dot)com> написал(а):
> > These drafts use reasonable concepts. Would you develop them into a
> > ready-to-commit patch? You may be able to translate your probabilistic test
> > procedures from https://gist.github.com/x4m/8b6025995eedf29bf588727375014dfc
> > into something like the src/bin/pgbench/t/001_pgbench_with_server.pl test of
> > pg_enum_oid_index.
>
> I'm working on it. Is it OK to use amcheck in pgbench tests? Or is it better to add the test to amcheck?

It could be okay, but I think it's better to add the test under amcheck. You
could still use pgbench in the test.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2021-07-23 22:53:19 Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Previous Message Heikki Linnakangas 2021-07-23 21:47:33 Re: IRe: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows