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

From Teodor Sigaev
Subject Re: WIP: Covering + unique indexes.
Date
Msg-id fc48f70f-6db6-4125-c8bd-d39d746ca58d@sigaev.ru
Whole thread Raw
In response to Re: WIP: Covering + unique indexes.  (Peter Geoghegan <pg@bowt.ie>)
Responses Sv: Re: WIP: Covering + unique indexes.  (Andreas Joseph Krogh <andreas@visena.com>)
Re: WIP: Covering + unique indexes.  (Peter Geoghegan <pg@bowt.ie>)
Re: WIP: Covering + unique indexes.  (Andres Freund <andres@anarazel.de>)
Re: WIP: Covering + unique indexes.  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
Thanks to everyone, pushed.




Peter Geoghegan wrote:
> On Sat, Apr 7, 2018 at 5:48 AM, Teodor Sigaev <teodor@sigaev.ru> wrote:
>> On close look, bts_btentry.ip_posid is not used anymore, I change
>> bts_btentry type to BlockNumber. As result, BTEntrySame() is removed.
> 
> That seems like a good idea.
> 
>> I'm not very happy with massive usage of
>> ItemPointerGetBlockNumberNoCheck(&(itup->t_tid)), suggest to  wrap it to
>> macro something like this:
>> #define BTreeInnerTupleGetDownLink(itup) \
>>          ItemPointerGetBlockNumberNoCheck(&(itup->t_tid))
> 
> Agreed. We do that with GIN.
> 

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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] path toward faster partition pruning
Next
From: Andreas Joseph Krogh
Date:
Subject: Sv: Re: WIP: Covering + unique indexes.