Message-ID: <47FC9A54.40006@postnewspapers.com.au>
Date: Wed, 09 Apr 2008 18:28:36 +0800
From: Craig Ringer <craig@postnewspapers.com.au>
User-Agent: Icedove 1.5.0.12 (X11/20070607)
MIME-Version: 1.0
To: Pavan Deolasee <pavan.deolasee@gmail.com>
Cc: "Luigi N. Puleio" <npuleio@rocketmail.com>,
	pgsql-performance@postgresql.org
Subject: Re: EXPLAIN detail
References: <862313.90586.qm@web33505.mail.mud.yahoo.com>
	<2e78013d0804090304l611044d6q4a71a927ec199b65@mail.gmail.com>
In-Reply-To: <2e78013d0804090304l611044d6q4a71a927ec199b65@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Pavan Deolasee wrote:

> Anyways, I don't think there is much
> tweaking you can do for such a query except making sure that
> your table is not bloated with dead tuples.

To the OP:

More explicitly: Make sure you use autovacuum or run VACUUM manually on
the table periodically.

Would I be correct in suspecting that your real problem is with a more
meaningful and complex query, and the one you've posted is
oversimplifying what you are trying to do? If that is the case, and
you're having problems with queries that do more real work than this one
does, maybe you should post EXPLAIN ANALYZE output from such a real
world query.

--
Craig Ringer