Re: WIP: Covering + unique indexes.

Teodor Sigaev <teodor@sigaev.ru>

From: Teodor Sigaev <teodor@sigaev.ru>
To: "Shinoda, Noriyoshi" <noriyoshi.shinoda@hpe.com>, Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Peter Geoghegan <pg@bowt.ie>, Jeff Janes <jeff.janes@gmail.com>, Anastasia Lubennikova <a.lubennikova@postgrespro.ru>
Date: 2018-04-09T14:56:44Z
Lists: pgsql-hackers
Thanks to both of you, pushed

Shinoda, Noriyoshi wrote:
> Hi!
> 
> Thank you for your response.
> 
> I think that it is good with your proposal.
> 
> Regards,
> 
> Noriyoshi Shinoda
> 
> *From:*Alexander Korotkov [mailto:a.korotkov@postgrespro.ru]
> *Sent:* Monday, April 9, 2018 11:22 PM
> *To:* Shinoda, Noriyoshi <noriyoshi.shinoda@hpe.com>
> *Cc:* PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>; Teodor Sigaev 
> <teodor@sigaev.ru>; Peter Geoghegan <pg@bowt.ie>; Jeff Janes 
> <jeff.janes@gmail.com>; Anastasia Lubennikova <a.lubennikova@postgrespro.ru>
> *Subject:* Re: WIP: Covering + unique indexes.
> 
> Hi!
> 
> On Mon, Apr 9, 2018 at 5:07 PM, Shinoda, Noriyoshi <noriyoshi.shinoda@hpe.com 
> <mailto:noriyoshi.shinoda@hpe.com>> wrote:
> 
>     I tested this feature and found a document shortage in the columns added to
>     the pg_constraint catalog.
>     The attached patch will add the description of the 'conincluding' column to
>     the manual of the pg_constraint catalog.
> 
> Thank you for pointing this!
> 
> I think we need more wordy explanation here.  My proposal is attached.
> 
> ------
> Alexander Korotkov
> Postgres Professional: http://www.postgrespro.com <http://www.postgrespro.com/>
> The Russian Postgres Company
> 

-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                    WWW: http://www.sigaev.ru/


Commits

  1. Adjust INCLUDE index truncation comments and code.

  2. Add commentary explaining why MaxIndexTuplesPerPage calculation is safe.

  3. Indexes with INCLUDE columns and their support in B-tree

  4. Add amcheck verification of heap relations belonging to btree indexes.

  5. Doc: move info for btree opclass implementors into main documentation.

  6. Doc: mention that you can't PREPARE TRANSACTION after NOTIFY.

  7. Remove dedicated B-tree root-split record types.

  8. Restructure index access method API to hide most of it at the C level.

  9. Split _bt_insertonpg to two functions.

  10. Major overhaul of btree index code. Eliminate special BTP_CHAIN logic for