Re: [HACKERS] WIP: Covering + unique indexes. - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [HACKERS] WIP: Covering + unique indexes.
Date
Msg-id CAH2-WzkTVrAcjKGA_XAM3R7bNnvtn_GsQVsvMEK_tFsnSm6YZA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] WIP: Covering + unique indexes.  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses Re: [HACKERS] WIP: Covering + unique indexes.
List pgsql-hackers
On Wed, Jan 17, 2018 at 12:45 AM, Andrey Borodin <x4mmm@yandex-team.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
checkedbt_index_parent_check() on master. 

I fixed that recently. It should be fine now.

--
Peter Geoghegan


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)
Next
From: Michael Paquier
Date:
Subject: Re: Use of term hostaddrs for multiple hostaddr values