| 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-23 16:33:18 |
| Message-ID: | 946242CB-D63A-4D7B-A5A5-485165F5B78A@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> 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?
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next 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 |
| Previous Message | Tom Lane | 2021-07-23 16:12:46 | Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared() |