pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Lubratt <mark.lubratt@indeq.com>
To: pgsql-performance@postgresql.org
Subject: Re: Correcting Hash Join Estimates
Date: Mon, 4 Apr 2005 01:15:38 -0500
Message-ID: <3de3144f9eb6c83400f8d41584af47f2@indeq.com> (raw)
In-Reply-To: <17973.1112594057@sss.pgh.pa.us>
References: <20050404050803.7175.qmail@webmail10.mesa1.secureserver.net>
	<17973.1112594057@sss.pgh.pa.us>


On Apr 4, 2005, at 12:54 AM, Tom Lane wrote:

> mark.lubratt@indeq.com writes:
>> I'm trying to optimize a query and the EXPLAIN ANALYZE (see link 
>> below)
>> shows that some hash join row estimates are wrong by a factor of 2-3,
>> and upwards of 7-8.
>
> I doubt that improving those estimates would lead to markedly better
> results.  You need to think about improving the view design instead.
> What context is this view used in --- do you just do "select * from
> view_get_all_user_award2", or are there conditions added to it, or
> perhaps it gets joined with other things?

Yes.  I forgot to show how the query is executed...

select * from view_get_all_user_award2 where person_id = 1;


>   Do you really need the
> DISTINCT constraint?

Yes.

> Do you really need the ORDER BY?

The customer wants an initial ordering in the displayed data.

> Can you
> simplify the WHERE clause at all?
>

I originally had a bunch of LEFT JOINs.  After reading Tow's "SQL 
Tuning", I was hoping to steer the planner into a more "optimal" plan 
by using a large where clause instead and doing the joins there (I 
think they're called implicit joins).  I was able to shave a couple of 
hundred milliseconds off the execution time by doing this.

> Half a second sounds pretty decent to me for a ten-way join with a 
> WHERE
> clause as unstructured as that.  If you really need it to execute in 
> way
> less time, you're probably going to have to rethink your data
> representation to make the query simpler.
>

Unfortunately, I'm not sure I can restructure the data.  I did consider 
materialized views.  However, they couldn't be lazy and that seemed 
like a lot of extra work for the backend for very little improvement.

If this sounds like decent performance to you...  I guess I can just 
tell the complainers that it's as good as it's going to get (barring a 
major hardware upgrade...).

Thanks!
Mark




view thread (3+ messages)

Message-ID: <3de3144f9eb6c83400f8d41584af47f2@indeq.com>
Permalink:  ../3de3144f9eb6c83400f8d41584af47f2@indeq.com/
Also on:    postgresql.org/message-id/3de3144f9eb6c83400f8d41584af47f2@indeq.com

 · 

reply

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: mark.lubratt@indeq.com
  Subject: Re: Correcting Hash Join Estimates
  In-Reply-To: <3de3144f9eb6c83400f8d41584af47f2@indeq.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