From: Craig Ringer <craig@postnewspapers.com.au>
To: Pavan Deolasee <pavan.deolasee@gmail.com>
Cc: Luigi N. Puleio <npuleio@rocketmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: EXPLAIN detail
Date: Wed, 09 Apr 2008 18:28:36 +0800
Message-ID: <47FC9A54.40006@postnewspapers.com.au> (raw)
In-Reply-To: <2e78013d0804090304l611044d6q4a71a927ec199b65@mail.gmail.com>
References: <862313.90586.qm@web33505.mail.mud.yahoo.com>
<2e78013d0804090304l611044d6q4a71a927ec199b65@mail.gmail.com>
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
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: craig@postnewspapers.com.au, pavan.deolasee@gmail.com, npuleio@rocketmail.com
Subject: Re: EXPLAIN detail
In-Reply-To: <47FC9A54.40006@postnewspapers.com.au>
* 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