From: Mike Nolan <nolan@gw.tssi.com>
To: kbottner@comcast.net
Cc: pgsql-performance@postgresql.org
Subject: Re: What's faster?
Date: Fri, 26 Dec 2003 19:06:21 -0600 (CST)
Message-ID: <200312270106.hBR16MLg002310@gw.tssi.com> (raw)
In-Reply-To: <008301c3cc0d$f3f337b0$7d00a8c0@juxtapose>
> Because Postgres requires VACUUM ANALYZE more frequently on updated tables,
> should I break this single field out into its own table, and if so what kind
> of a speed up can I expect to achieve. I would be appreciative of any
> guidance offered.
Unless that field is part of the key, I wouldn't think that a vacuum
analyze would be needed, as the key distribution isn't changing.
I don't know if that is still true if that field is indexed. Tom?
Even then, as I understand things vacuum analyze doesn't rebuild indexes,
so I could see a need to drop and rebuild indexes on a regular basis,
even if you move that field into a separate table.
--
Mike Nolan
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: nolan@gw.tssi.com, kbottner@comcast.net
Subject: Re: What's faster?
In-Reply-To: <200312270106.hBR16MLg002310@gw.tssi.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