pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Markus Bertheau <twanger@bluetwanger.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: postgres sql list <pgsql-sql@postgresql.org>
Subject: Re: strange query execution times
Date: 05 Oct 2001 08:48:57 +0200
Message-ID: <1002264548.15228.1.camel@entwicklung01.cenes.de> (raw)
In-Reply-To: <9106.1002037789@sss.pgh.pa.us>
References: <1001958754.2485.31.camel@entwicklung01.cenes.de>
	<9106.1002037789@sss.pgh.pa.us>

On Tue, 2001-10-02 at 17:49, Tom Lane wrote:
> Markus Bertheau <twanger@bluetwanger.de> writes:
> > r_kunden_anbieter describes the relationship between customers and
> > suppliers. there are five status, 0 to 4 in attribute beziehung. both
> > queries return the same results. they select all customers which have a
> > certain relationship (beziehung = 3) to a given supplier.
> > personen has 484 rows, r_kunden_anbieter 327.
> 
> How many rows actually satisfy "rka.a_id = 620 and rka.beziehung = 3"?
> 
> The issue appears to be that the planner estimates one matching row
> in the one case and two matching rows in the second.  Given the estimate
> of one row, it decides to go for the low-overhead nested loop plan.
> I am guessing that there are really considerably more than two matching
> rows, and so the nested loop plan loses badly compared to the mergejoin,
> which takes longer to set up but is better able to cope with many rows.
> 
> FWIW, 7.2 has better statistics and should be better able to pick the
> right plan in this context ...

13 rows do. Is there a way to force 7.0.3 (or 7.1.3) to use the
mergejoin with the straightforward condition?

Markus Bertheau
Cenes Data GmbH





view thread (3+ messages)

Message-ID: <1002264548.15228.1.camel@entwicklung01.cenes.de>
Permalink:  ../1002264548.15228.1.camel@entwicklung01.cenes.de/
Also on:    postgresql.org/message-id/1002264548.15228.1.camel@entwicklung01.cenes.de

 · 

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-sql@postgresql.org
  Cc: twanger@bluetwanger.de, tgl@sss.pgh.pa.us
  Subject: Re: strange query execution times
  In-Reply-To: <1002264548.15228.1.camel@entwicklung01.cenes.de>

* 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