Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group