From: Heikki Linnakangas <heikki@enterprisedb.com>
To: PFC <lists@peufeu.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Short row header
Date: Wed, 20 Jun 2007 09:36:05 +0100
Message-ID: <4678E6F5.6040300@enterprisedb.com> (raw)
In-Reply-To: <op.tt7mw6dccigqcu@apollo13>
References: <op.tt7mw6dccigqcu@apollo13>
PFC wrote:
>
> I have this "poll results" table with just 3 integer fields, which
> is never updated, only inserted/deleted...
> Did the Devs consider an option to have VACUUM reduce the row header
> sizes for tuples that are long commited and are currently visible to all
> transactions ?
That has been suggested before, but IIRC it wasn't considered to be
worth it. It would only save 4 bytes (the xmin field) per tuple, the
free space would be scattered around all pages making it less useful,
and having to deal with two different header formats would make
accessing the header fields more complex.
> (even if this makes the tuples non-updateable, as long as
> they can be deleted, it would be OK for this type of tables).
That would save another 6 bytes per tuple (ctid field), but we generally
stay away from things that impose limitations like that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: heikki@enterprisedb.com, lists@peufeu.com
Subject: Re: Short row header
In-Reply-To: <4678E6F5.6040300@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox