Re: optimizer picks smaller table to drive nested loops?

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.