From: Josh Berkus <josh@agliodbs.com>
To: Dennis Bjorklund <db@zigo.dhs.org>
To: Jeff <threshar@torgo.978.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Fixed width rows faster?
Date: Fri, 5 Mar 2004 15:37:02 -0800
Message-ID: <200403051537.02535.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0403051525560.13979-100000@zigo.dhs.org>
References: <Pine.LNX.4.44.0403051525560.13979-100000@zigo.dhs.org>
Jeff:
> As far as I know there is only a small win when you want to extract some
> field from a tuple and with variable width fields you have to walk to the
> correct field. But this is a small performance problem unless you have
> very many variable size columns in the table.
BTW, Dennis here is not talking about CHAR; CHAR is handled as a
variable-length field in Postgres. INTEGER is a fixed-width field.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, db@zigo.dhs.org, threshar@torgo.978.org
Subject: Re: Fixed width rows faster?
In-Reply-To: <200403051537.02535.josh@agliodbs.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