pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mike Mascari <mascarm@mascari.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow execution time when querying view with WHERE clause
Date: Wed, 24 Nov 2004 17:51:13 -0500
Message-ID: <41A51061.30805@mascari.com> (raw)
In-Reply-To: <4738.1101277883@sss.pgh.pa.us>
References: <41A25C3B.3040608@mascari.com>
	<28237.1101232445@sss.pgh.pa.us>
	<41A42409.7080704@mascari.com>
	<4738.1101277883@sss.pgh.pa.us>

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





view thread (8+ messages)

Message-ID: <41A51061.30805@mascari.com>
Permalink:  ../41A51061.30805@mascari.com/
Also on:    postgresql.org/message-id/41A51061.30805@mascari.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: mascarm@mascari.com, tgl@sss.pgh.pa.us
  Subject: Re: Slow execution time when querying view with WHERE clause
  In-Reply-To: <41A51061.30805@mascari.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox