Re: Allow to specify #columns in heap/index_form_tuple - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Allow to specify #columns in heap/index_form_tuple
Date
Msg-id CAH2-Wz=6700bysb0_K96wER_AWaue4qxnO=0NbQBGnL1KFnzKQ@mail.gmail.com
Whole thread Raw
In response to Allow to specify #columns in heap/index_form_tuple  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
I don't see why you'd necessarily need to know where in the index the tuple came from under my proposal. Besides, as I already pointed out, we already hard code minus infinity handling within internal pages during tuple comparisons. 

Anastasia's patch could modify nbtree in exactly the same way as suffix truncation would. I see no conflict there. Quite the opposite, in fact.

--
Peter Geoghegan
(Sent from my phone)

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [sqlsmith] Failed assertion in _hash_kill_items/MarkBufferDirtyHint
Next
From: Tom Lane
Date:
Subject: Re: postgres_fdw IMPORT SCHEMA and partitioned tables