Re: [HACKERS] WIP: Covering + unique indexes.

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [HACKERS] WIP: Covering + unique indexes.
Date: 2018-01-20 22:36:13
Message-ID: CAH2-WzkTVrAcjKGA_XAM3R7bNnvtn_GsQVsvMEK_tFsnSm6YZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 17, 2018 at 12:45 AM, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> Unfortunately, amcheck_next does not work currently on HEAD (there are problems with AllocSetContextCreate() signature), but I've tested bt_index_check() before, during and after pgbench, on primary and on slave. Also, I've checked bt_index_parent_check() on master.

I fixed that recently. It should be fine now.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-01-20 22:39:21 Re: Use of term hostaddrs for multiple hostaddr values
Previous Message Peter Geoghegan 2018-01-20 20:09:23 Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)