Re: Save a few bytes in pg_attribute
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-03-21T20:11:46Z
Lists: pgsql-hackers
Hi, On 2023-03-21 15:26:38 -0400, Tom Lane wrote: > Matthias van de Meent <boekewurm+postgres@gmail.com> writes: > > ... with that patch we actually don't need the attcacheoff in the > > pg_atttribute struct: it only needs to be present in the derived > > "TupleAttrAlignData" structs which carry the > > length/alignment/storage/byval info. > > Yeah, I was wondering about that too: keeping attcacheoff as local > state in slots might get us all its win without so much conceptual > dirtiness. It's also the place where it's the least likely to help - afaict attcacheoff is only really beneficial for fastgetattr(). Which conditions it's use more strictly - not only can there not be any NULLs before the accessed column, there may not be any NULLs in the tuple at all. Greetings, Andres Freund
Commits
-
Save a few bytes in pg_attribute
- 90189eefc1e1 16.0 landed