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

From Tom Lane
Subject Re: Allow to specify #columns in heap/index_form_tuple
Date
Msg-id 14063.1490987035@sss.pgh.pa.us
Whole thread Raw
In response to Re: Allow to specify #columns in heap/index_form_tuple  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Mar 31, 2017 at 2:32 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> It just seems way too dangerous.

> So, we end up with heap tuples with different numbers of attributes
> all the time, whenever you add a column.  It works fine - on decoding,
> the additional columns will be treated as null (unless somebody
> commits Serge Rielau's patch, which regrettably nobody has gotten
> around to reviewing).  Why is this case different?

The reason it works fine for heap tuples is that heap tuple headers
explicitly record the number of attributes in the tuple.  Index
tuples don't.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Brandur Leach
Date:
Subject: Re: [PATCH] SortSupport for macaddr type
Next
From: Jeff Janes
Date:
Subject: Re: Patch: Write Amplification Reduction Method (WARM)