From: Josh Berkus <josh@agliodbs.com>
To: David Roussel <pgsql-performance@diroussel.xsmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: How can an index be larger than a table
Date: Thu, 21 Apr 2005 10:31:51 -0700
Message-ID: <200504211031.51567.josh@agliodbs.com> (raw)
In-Reply-To: <1114078390.26441.232391808@webmail.messagingengine.com>
References: <1114078390.26441.232391808@webmail.messagingengine.com>
David,
> What also seems weird to me is that the control table has some unique
> indexes created on it, but the data_upate_events table just has a unique
> constraint. Will postgres use an index in the background to enforce
> this constraint?
If you somehow have a unique constraint without a unique index, something is
seriously broken. I suspect hacking of system tables.
Otherwise, it sounds like you have index bloat due to mass deletions. Run
REINDEX, or, preferably, VACUUM FULL and then REINDEX.
--
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, pgsql-performance@diroussel.xsmail.com
Subject: Re: How can an index be larger than a table
In-Reply-To: <200504211031.51567.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