Re: remove ATTRIBUTE_FIXED_PART_SIZE - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: remove ATTRIBUTE_FIXED_PART_SIZE
Date
Msg-id b451700a-5e7d-5bf7-e3af-b993cc02ed31@2ndquadrant.com
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 18/08/2018 23:05, Tom Lane wrote:
> Possibly we need to be more careful than we are now about whether
> there's padding at the end of the fixed-size fields ... but just
> ripping out the code that attempts to deal with that is hardly
> an improvement.

I don't think the tuple packing issue has to do with the tuple
descriptor code.  The tuple descriptors already use allocations of size
sizeof(FormData_pg_attribute) (CreateTemplateTupleDesc), just the memcpy
and memset calls use (potentially) less.  That might have saved a few
bytes for omitting the varlena fields, but I don't think it affects
alignment correctness.  If we, say, added a trailing char field now, the
only thing this code

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [FEATURE PATCH] pg_stat_statements with plans (v02)
Next
From: Peter Eisentraut
Date:
Subject: Re: remove ATTRIBUTE_FIXED_PART_SIZE