On Wed, Sep 10, 2014 at 11:43:52AM -0400, Robert Haas wrote: > But there are a couple of obvious problems with this idea, too, such as: > > 1. It's really complicated and a ton of work. > 2. It would break pg_upgrade pretty darn badly unless we employed some > even-more-complex strategy to mitigate that. > 3. The savings might not be enough to justify the effort. > > It might be interesting for someone to develop a tool measuring the > number of bytes of alignment padding we lose per tuple or per page and > gather some statistics on it on various databases. That would give us > some sense as to the possible savings.
And will we ever implement a logical attribute system so we can reorder the stored attribtes to minimize wasted space? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
