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 17:11:24
Message-ID: AANLkTi=VFJFoPf2vRVH0+w-+5jt_Z8Wp+V7OdLdEmBa1@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Mon, Jan 17, 2011 at 8:23 AM, Tim Uckun <timuckun(at)gmail(dot)com> wrote:
>> 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');
>
>        relname         | pg_relation_size |  reltuples  | relpages
> ------------------------+------------------+-------------+----------
>  consolidated_urls      |       1303060480 | 1.80192e+06 |   159065
>  consolidated_urls_pkey |        114745344 | 1.80192e+06 |    14007
> (2 rows)

Hmm, I was thinking that the table might be bloated but it's not
obvious from this.

I think you might have the same general kind of problem reported here:

http://archives.postgresql.org/pgsql-bugs/2009-09/msg00259.php

and here:

http://archives.postgresql.org/pgsql-performance/2010-04/msg00139.php

...and there are other reports as well.

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

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2011-01-17 18:17:03
Subject: Re: BUG #5840: Updating arrays using subscripted assignment results in uninitialized values
Previous:From: Alvaro HerreraDate: 2011-01-17 16:09:56
Subject: Re: BUG #5835: PL/Python crashes

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