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

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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tim Uckun <timuckun(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Problems with adding a is not null to a query.
Date: 2011-01-17 13:21:13
Message-ID: AANLkTi=6wYtWRURpUtBgJcZEMPGUne+emSmxL_sGbP6y@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Sun, Jan 16, 2011 at 5:47 PM, Tim Uckun <timuckun(at)gmail(dot)com> wrote:
>> 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).
>
>
> The analyze finished. I re-ran the explain it was still taking a very
> long time. I stopped it eventually.

Hmm.  What do you get for:

SELECT relname, pg_relation_size(oid), reltuples, relpages FROM
pg_class WHERE relname IN ('consolidated_urls',
'consolidated_urls_pkey');

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-bugs by date

Next:From: Tim UckunDate: 2011-01-17 13:23:56
Subject: Re: Problems with adding a is not null to a query.
Previous:From: Jeff TurnerDate: 2011-01-17 10:34:29
Subject: BUG #5841: rank()+1 fails, 1+rank() succeeds

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