From: Gregory Stark <stark@enterprisedb.com>
To: "PFC" <lists@peufeu.com>
Cc: <pgsql-performance@postgresql.org>
Subject: Re: Short row header
In-Reply-To: <op.tt7mw6dccigqcu@apollo13> (lists@peufeu.com's message of "Wed,
	20 Jun 2007 09:54:32 +0200")
Organization: EnterpriseDB
References: <op.tt7mw6dccigqcu@apollo13>
Date: Wed, 20 Jun 2007 10:05:47 +0100
Message-ID: <87tzt3f11w.fsf@oxford.xeocode.com>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


"PFC" <lists@peufeu.com> writes:

> 	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 ? (even if this makes the tuples non-updateable, as long as  they
> can be deleted, it would be OK for this type of tables).

It wouldn't actually speed up anything unless the space it frees up was then
used by something. That would mean loading one of your polls into the small
bits of space freed up in every page. For most tables like this you want to do
large bulk loads and want your loads stored quickly in contiguous space so it
can be accessed quickly, not spread throughout the table.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com