Re: Problems with adding a is not null to a query.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tim Uckun <timuckun(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Problems with adding a is not null to a query.
Date: 2011-01-16 17:15:34
Message-ID: 9026.1295198134@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tim Uckun <timuckun(at)gmail(dot)com> writes:
>> Possibly the table's never been ANALYZEd ... do you have autovacuum
>> enabled?

> I do have autovacuum enabled and I am running 8.4

Hmm, autovacuum *should* have been keeping track of things for you,
but it might still be worth doing a manual ANALYZE against that table
to see if the estimated rowcount changes. If not, you'll need to raise
the statistics target for that column (and again ANALYZE).

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tim Uckun 2011-01-16 22:10:08 Re: Problems with adding a is not null to a query.
Previous Message Denish Patel 2011-01-16 16:06:42 Re: date_trunc check constraint causes errors when restoring in a db with a different time zone