Re: Allow to specify #columns in heap/index_form_tuple

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Allow to specify #columns in heap/index_form_tuple
Date: 2017-03-31 19:43:42
Message-ID: CAH2-Wz=6700bysb0_K96wER_AWaue4qxnO=0NbQBGnL1KFnzKQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-03-31 19:55:30 Re: postgres_fdw IMPORT SCHEMA and partitioned tables
Previous Message Robert Haas 2017-03-31 19:38:30 Re: [sqlsmith] Failed assertion in _hash_kill_items/MarkBufferDirtyHint