Postgres Pro
Downloads
Home   >   mailing lists

Re: Problems with adding a is not null to a query. - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Problems with adding a is not null to a query.
Date
Msg-id 20744.1295297840@sss.pgh.pa.us
Whole thread Raw
In response to Re: Problems with adding a is not null to a query.  (Tim Uckun <timuckun@gmail.com>)
Responses Re: Problems with adding a is not null to a query.  (Tim Uckun <timuckun@gmail.com>)
List pgsql-bugs
Tree view 
Tim Uckun <timuckun@gmail.com> writes:
>         relname         | pg_relation_size |  reltuples  | relpages
> ------------------------+------------------+-------------+----------
>  consolidated_urls      |       1303060480 | 1.80192e+06 |   159065
>  consolidated_urls_pkey |        114745344 | 1.80192e+06 |    14007

With a table that large, you're probably going to need a larger stats
target in order to get reasonable estimates for low-frequency values.
Am I right in guessing that pg_stats.n_distinct is much too low for
the domain_id column?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5840: Updating arrays using subscripted assignment results in uninitialized values
Next
From: Tim Uckun
Date:
Subject: Re: Problems with adding a is not null to a query.