From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: david@shadovitz.com <david@shadovitz.com>
Cc: 'pgsql-performance@postgresql.org' <pgsql-performance@postgresql.org>
Subject: Re: Query plan - now what?
Date: Fri, 12 Dec 2003 14:44:05 +0530
Message-ID: <3FD986DD.7000909@persistent.co.in> (raw)
In-Reply-To: <01C3C045.7EDD13C0.david@shadovitz.com>
References: <01C3C045.7EDD13C0.david@shadovitz.com>
David Shadovitz wrote:
> Well, now that I have the plan for my slow-running query, what do I do? Where
> should I focus my attention?
Briefly looking over the plan and seeing the estimated v/s actual row mismatch,I
can suggest you following.
1. Vacuum(full) the database. Probably you have already done it.
2. Raise statistics_target to 500 or more and reanalyze the table(s) in question.
3. Set enable_hash_join to false, before running the query and see if it helps.
HTH
Shridhar
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: shridhar_daithankar@persistent.co.in, david@shadovitz.com
Subject: Re: Query plan - now what?
In-Reply-To: <3FD986DD.7000909@persistent.co.in>
* 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