Tom Lane <[EMAIL PROTECTED]> writes: > "Ryan Bradetich" <[EMAIL PROTECTED]> writes: >> The patch concept is fairly simple. > >> 1. Add a new boolean local variable: require_max_align >> (initialized to false). > > This really can't possibly work, because you'd need to propagate > knowledge of the tuple's alignment requirement all over the place. > In particular, how would code *reading* the tuple know where the > data starts?
Uh, at t_hoff, no? > Also, I don't think you get (very much of) the actual benefit unless the > code that inserts tuples into disk pages knows to do something different in > the int-align case. +1 -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
