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

From Robert Haas
Subject Re: Allow to specify #columns in heap/index_form_tuple
Date
Msg-id CA+TgmobQR2svk1BG=rrQFWqrt_O6YQ3cKaKgpZFmhcKhPHw7ow@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
On Fri, Mar 31, 2017 at 1:24 PM, Andres Freund <andres@anarazel.de> wrote:
> The covering indexes patch [1] really needs a version of
> heap_form_tuple/index_form_tuple that allows to specify the number of
> columns in the to-be generated tuple.  Previously the faster expression
> evaluation stuff could also have benefited form the same for both
> forming and deforming tuples.
>
> It's obviously trivial to add, codewise.
>
> I think for index_form_tuple we can just add a parameter, but for
> heap_form_tuple/heap_deform_tuple that'd probably break a number of
> external users.  How about adding _ex variants that allow to specify
> that?

I think our usual practice is _extended rather than just _ex, but no
objections otherwise.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] Transaction traceability - txid_status(bigint)
Next
From: Masahiko Sawada
Date:
Subject: Some never executed code regarding the table sync worker