AW: Re: Performance degradation in PostgreSQL 7.1beta3 vs 6.5.3 - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: Re: Performance degradation in PostgreSQL 7.1beta3 vs 6.5.3
Date
Msg-id 11C1E6749A55D411A9670001FA6879633681B9@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
Responses Re: AW: Re: Performance degradation in PostgreSQL 7.1beta3 vs 6.5.3
List pgsql-hackers
> > More importantly, PostgreSQL 6.5.3 works very, very well without
> > VACUUM'ing.
> 
> 6.5 effectively assumes that "foo = constant" will select exactly one
> row, if it has no statistics to prove otherwise.

I thought we had agreed upon a default that would still use
the index in the above case when no statistics are present.
Wasn't it something like a 5% estimate ? I did check
that behavior, since I was very concerned about that issue. 
Now, what is so different in his case?

Andreas


pgsql-hackers by date:

Previous
From: Zeugswetter Andreas SB
Date:
Subject: AW: AW: AW: Re: tinterval - operator problems on AIX
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: AW: AW: Re: tinterval - operator problems on AIX