Re: [GENERAL] [PGSQL v8.2.5] Similar queries behave differently

2007-10-29 Thread Reg Me Please
Hai all again. Maybe I've solved the problem, but would like to have some hint on "why". In the second query I've substituted the last join (natural join tt_rice) with an additional "where condition". I can do this as I am sure that the tt_rice table will always contain just one row with one fiel

Re: [GENERAL] [PGSQL v8.2.5] Similar queries behave differently

2007-10-25 Thread Scott Marlowe
On 10/25/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > Il Thursday 25 October 2007 13:20:40 Gregory Stark ha scritto: > > "Gregory Stark" <[EMAIL PROTECTED]> writes: > > > "Reg Me Please" <[EMAIL PROTECTED]> writes: > > >>-> Seq Scan on tt_elem (cost=0.00..29.40 rows=1940 > > >>

Re: [GENERAL] [PGSQL v8.2.5] Similar queries behave differently

2007-10-25 Thread Reg Me Please
Il Thursday 25 October 2007 13:20:40 Gregory Stark ha scritto: > "Gregory Stark" <[EMAIL PROTECTED]> writes: > > "Reg Me Please" <[EMAIL PROTECTED]> writes: > >>-> Seq Scan on tt_elem (cost=0.00..29.40 rows=1940 > >> width=8) (actual time=0.012..0.013 rows=1 loops=1) > > > > The d

Re: [GENERAL] [PGSQL v8.2.5] Similar queries behave differently

2007-10-25 Thread Gregory Stark
"Gregory Stark" <[EMAIL PROTECTED]> writes: > "Reg Me Please" <[EMAIL PROTECTED]> writes: > >>-> Seq Scan on tt_elem (cost=0.00..29.40 rows=1940 width=8) >> (actual time=0.012..0.013 rows=1 >> loops=1) > > The discrepancy etween the estim

Re: [GENERAL] [PGSQL v8.2.5] Similar queries behave differently

2007-10-25 Thread Gregory Stark
"Reg Me Please" <[EMAIL PROTECTED]> writes: >-> Seq Scan on tt_elem (cost=0.00..29.40 rows=1940 width=8) > (actual time=0.012..0.013 rows=1 > loops=1) The discrepancy etween the estimated rows and actual rows makes me think you've not a