pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Ceri Storey <cez@necrofish.org.uk>
Cc: pgsql-performance@postgresql.org
Subject: Re: Join optimisation Quandry
Date: Fri, 16 Jan 2004 22:05:54 -0800 (PST)
Message-ID: <20040116220146.N81715@megazone.bigpanda.com> (raw)
In-Reply-To: <20040117010334.GA43530@mrtall.compsoc.man.ac.uk>
References: <20040114231014.GE53284@mrtall.compsoc.man.ac.uk>
	<20040116094935.P66040@megazone.bigpanda.com>
	<20040117010334.GA43530@mrtall.compsoc.man.ac.uk>

On Sat, 17 Jan 2004, Ceri Storey wrote:

> On Fri, Jan 16, 2004 at 10:17:50AM -0800, Stephan Szabo wrote:
> > As a starting point, we're likely to need the exact query, explain analyze
> > output for the query and version information.
>
> Okay, from top to bottom:
>
>   SELECT p1.chan_name, p1.prog_start AS now_start, p1.prog_id, p1.title_text,
>     p2.prog_start AS next_start, p2.prog_id, p2.title_text,
>     p1.title_wanted, p2.title_wanted, p1.chan_id
>   FROM (programme natural join channel NATURAL JOIN title) AS p1
>     LEFT OUTER JOIN (programme NATURAL JOIN title) AS p2
>     ON p1.prog_next = p2.prog_id
>   WHERE p1.prog_start <= timestamp 'now' AND p1.prog_stop > timestamp 'now'
>   ORDER BY p1.chan_id ASC
>

Well the plan would seems reasonable to me if there really was only 1 row
coming from the where conditions on p1.  As a first step, if you raise the
statistics target (see ALTER TABLE) for prog_start and prog_stop and
re-analyze the table, do you get a better estimate of the rows from that
condition? Secondly, what do you get if you enable_nestloop=off before
explain analyzing the query?



view thread (7+ messages)  latest in thread

Message-ID: <20040116220146.N81715@megazone.bigpanda.com>
Permalink:  ../20040116220146.N81715@megazone.bigpanda.com/
Also on:    postgresql.org/message-id/20040116220146.N81715@megazone.bigpanda.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: sszabo@megazone.bigpanda.com, cez@necrofish.org.uk
  Subject: Re: Join optimisation Quandry
  In-Reply-To: <20040116220146.N81715@megazone.bigpanda.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