Re: remove ATTRIBUTE_FIXED_PART_SIZE - Mailing list pgsql-hackers

From Andres Freund
Subject Re: remove ATTRIBUTE_FIXED_PART_SIZE
Date
Msg-id D242153C-0865-47AD-AC76-FB148E0B84C7@anarazel.de
Whole thread Raw
In response to Re: remove ATTRIBUTE_FIXED_PART_SIZE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: remove ATTRIBUTE_FIXED_PART_SIZE
List pgsql-hackers

On August 18, 2018 8:37:00 PM GMT+02:00, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
>> Since the introduction of the CATALOG_VARLEN stuff, the fixed size of
>> pg_attribute is exactly sizeof(FormData_pg_attribute), so the ancient
>> mechanism to track the fixed size manually using
>> ATTRIBUTE_FIXED_PART_SIZE can be removed.
>
>Meh, I'm not sure about this.  What about the possibility of trailing
>padding after the last fixed column, as the comment you propose to
>remove is talking about?  Sure, we don't have that today, but we
>might again the next time somebody adds a column to pg_attribute.

Where would avoiding that padding be an important thing her? Strictly speaking it's not even safe to access the last
memberswithout the padding present - the compiler is free to store with a wider write if that just affects padding. GCC
doesthat in some cases IIRC. 

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Allowing printf("%m") only where it actually works
Next
From: Tom Lane
Date:
Subject: Re: remove ATTRIBUTE_FIXED_PART_SIZE