Re: Slow execution time when querying view with WHERE clause

From: Mike Mascari <mascarm(at)mascari(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Slow execution time when querying view with WHERE clause
Date: 2004-11-24 22:51:13
Message-ID: 41A51061.30805@mascari.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Tom Lane wrote:
> Um ... doh ... analyze.c about line 1550:
>
> /* We can only compute valid stats if we found some non-null values. */
> if (nonnull_cnt > 0)
> ...
>
> There's a bit of an epistemological issue here: if we didn't actually
> find any nonnull values in our sample, is it legitimate to assume that
> the column is entirely null? On the other hand, if we find only "3" in
> our sample we will happily assume the column contains only "3", so I
> dunno why we are discriminating against null. This seems like a case
> that just hasn't come up before.

Will this discriminatory policy toward null end for 8.0?

Mike Mascari

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Steinar H. Gunderson 2004-11-25 01:18:23 Re: Postgres vs. MySQL
Previous Message gnari 2004-11-24 19:12:41 Re: FW: Index usage