pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Hiroshi Inoue <Inoue@tpf.co.jp>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Stoyan Genov <genov@digsys.bg>
Cc: Dirk Lutzebaeck <lutzeb@aeccom.com>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Howto to force NULL rows at the bottom ?
Date: Mon, 6 Dec 1999 08:37:04 -0500 (EST)
Message-ID: <199912061337.IAA18651@candle.pha.pa.us> (raw)
In-Reply-To: <14944.944453719@sss.pgh.pa.us>

> After further thought I think the goal of making explicit sort order
> always match btree index results is unreachable, because the explicit
> sort hasn't got enough information.  All it has is an operator ID, and
> that's about all it can possibly have, at least in the "USING operator"
> case.  But btree ordering doesn't depend on an operator ID, it depends
> on an opclass.  The counterexample goes like this: I could easily make
> two different opclasses, "int_forward" and "int_reverse", that both work
> on int4 data but produce opposite btree sort orders.  They're even built
> from the same operators, just lined up differently.  Now, how shall an
> explicit sort decide which btree ordering to conform to?  Indeed, if
> I make two indexes on the same table using the two opclasses, it's not
> even predictable which ordering an index-driven sort will return.
> 
> This counterexample is a bit farfetched of course, but it shows that
> there is no theoretically-pure answer.  We have to make some unprovable
> assumptions about what to do.

But if we have an operator, shouldn't we just look for < and > and use
them if we have those symbols?  Seems like it would be better than what
we have, if not perfect.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (12+ messages)

Message-ID: <199912061337.IAA18651@candle.pha.pa.us>
Permalink:  ../199912061337.IAA18651@candle.pha.pa.us/
Also on:    postgresql.org/message-id/199912061337.IAA18651@candle.pha.pa.us

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, Inoue@tpf.co.jp, peter_e@gmx.net, genov@digsys.bg, lutzeb@aeccom.com
  Subject: Re: [SQL] Howto to force NULL rows at the bottom ?
  In-Reply-To: <199912061337.IAA18651@candle.pha.pa.us>
  References: <14944.944453719@sss.pgh.pa.us> <199912061337.IAA18651@candle.pha.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