Re: WIP: Covering + unique indexes.

Andrew Borodin <borodin@octonica.com>

From: Andrew Borodin <borodin@octonica.com>

To: Anastasia Lubennikova <a.lubennikova@postgrespro.ru>

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, Anastasia Lubennikova <lubennikovaav@gmail.com>

Date: 2016-08-17T07:36:53Z

Lists: pgsql-hackers

> That was a bug caused by high key truncation, that occurs when index has more than 3 levels. Fixed.
Affirmative. I've tested index construction with 100M rows and
subsequent execution of select queries using index, works fine.

Best regards, Andrey Borodin, Octonica & Ural Federal University.

Commits

Adjust INCLUDE index truncation comments and code.
- 075aade4361b 11.0 landed
Add commentary explaining why MaxIndexTuplesPerPage calculation is safe.
- 2a67d6440db4 11.0 cited
Indexes with INCLUDE columns and their support in B-tree
- 8224de4f42cc 11.0 landed
Add amcheck verification of heap relations belonging to btree indexes.
- 7f563c09f890 11.0 cited
Doc: move info for btree opclass implementors into main documentation.
- 3785f7eee3d9 11.0 cited
Doc: mention that you can't PREPARE TRANSACTION after NOTIFY.
- e4fbf22831c2 11.0 cited
Remove dedicated B-tree root-split record types.
- 0c504a80cf2e 11.0 cited
Restructure index access method API to hide most of it at the C level.
- 65c5fcd353a8 9.6.0 cited
Split _bt_insertonpg to two functions.
- bc292937ae6a 8.3.0 cited
Major overhaul of btree index code. Eliminate special BTP_CHAIN logic for
- 9e85183bfc31 7.1.1 cited