Re: optimizer picks smaller table to drive nested loops?

From: Randy Neumann <Randy_Neumann(at)centralref(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: optimizer picks smaller table to drive nested loops?
Date: 2003-07-07 20:58:54
Message-ID: 200307072115.PAA52502@mail.simn.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Monday 07 July 2003 12:22 pm, you wrote:

> loops=1) -> Seq Scan on region (cost=0.00..2813.00 rows=2767 width=104)
> (actual time=0.03..123.44 rows=2767 loops=2) Total runtime: 566.24 msec
> (9 rows)
>
> (I'm also a bit puzzled why the optimizer is calculating that 2,813 * 2 =
> 5,534)

You should read it 2767 (rows) * 2 = 5534 (rows)
2813.00 is part of the cost.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jim C. Nasby 2003-07-07 21:40:48 Re: Moving postgresql.conf tunables into 2003...
Previous Message scott.marlowe 2003-07-07 19:58:24 Re: PostgreSQL vs. MySQL