From: Tom Lane <tgl@sss.pgh.pa.us>
To: mailreg@numerixtechnology.de
Cc: Greg Stark <gsstark@mit.edu>
Cc: pgsql-sql@postgresql.org
Subject: Re: ORDER BY and NULLs
Date: Sun, 19 Sep 2004 16:30:29 -0400
Message-ID: <21812.1095625829@sss.pgh.pa.us> (raw)
In-Reply-To: <414DEA7F.6050100@numerixtechnology.de>
References: <011d01c49e5b$c88fdb20$2766f30a@development.greatgulfhomes.com>
<414DB1AB.5080207@sympatico.ca>
<414DB594.5000300@numerixtechnology.de>
<19733.1095613137@sss.pgh.pa.us>
<414DBF6D.8040500@numerixtechnology.de>
<87zn3mjeaw.fsf@stark.xeocode.com>
<414DEA7F.6050100@numerixtechnology.de>
T E Schmitz <mailreg@numerixtechnology.de> writes:
> Greg Stark wrote:
>> Which book is it?
> PostgreSQL by Korry Douglas + Susan Douglas, ISBN 0-7357-1257-3; Feb 2003
Hmm, I've heard of that book but never seen it. The authors are not
participants in the PG community --- AFAICT neither of them have ever
posted anything in the mailing lists.
> The paragraph continues:
> "If the SELECT command included the clause WHERE phone NOT NULL,
> PostgreSQL could use the index to satisfy the ORDER BY clause.
> An index that covers optional (NOT NULL) columns will not be used to
> speed table joins either."
My goodness, it seems to be a veritable fount of misinformation :-(
I wonder how much of this is stuff that is true for Oracle and they just
assumed it carried over?
regards, tom lane
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, mailreg@numerixtechnology.de, gsstark@mit.edu
Subject: Re: ORDER BY and NULLs
In-Reply-To: <21812.1095625829@sss.pgh.pa.us>
* 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