Re: Optimizer showing wrong rows in plan - Mailing list pgsql-performance

From Tom Lane
Subject Re: Optimizer showing wrong rows in plan
Date
Msg-id 24446.1269797854@sss.pgh.pa.us
Whole thread Raw
In response to Re: Optimizer showing wrong rows in plan  (Jeremy Harris <jgh@wizmail.org>)
Responses Re: Optimizer showing wrong rows in plan  (Tadipathri Raghu <traghu.dba@gmail.com>)
List pgsql-performance
Jeremy Harris <jgh@wizmail.org> writes:
> On 03/28/2010 05:27 PM, Tom Lane wrote:
>> This is intentional: the size estimates for a never-yet-analyzed
>> table are *not* zero.  This is because people frequently create and load
>> up a table and then immediately query it without an explicit ANALYZE.

> Does the creation of an index also populate statistics?

IIRC, it will set the relpages/reltuples counts (though not any
more-complex statistics); but only if the table is found to not be
completely empty.  Again, this is a behavior designed with common
usage patterns in mind, to not set relpages/reltuples to zero on a
table that's likely to get populated shortly.

            regards, tom lane

pgsql-performance by date:

Previous
From: Jeremy Harris
Date:
Subject: Re: Optimizer showing wrong rows in plan
Next
From: Cédric Villemain
Date:
Subject: Re: Forcing index scan on query produces 16x faster