Re: pgsql/src include/utils/tuplesort.h backend/ut ...

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)hub(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql/src include/utils/tuplesort.h backend/ut ...
Date: 2001-06-02 19:11:17
Message-ID: 200106021911.f52JBH321447@candle.pha.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers


TODO updated:

* -Make NULL's come out at the beginning or end depending on the
ORDER BY direction (Tom)

> CVSROOT: /home/projects/pgsql/cvsroot
> Module name: pgsql
> Changes by: tgl(at)hub(dot)org 01/06/02 15:01:53
>
> Modified files:
> src/include/utils: tuplesort.h
> src/backend/utils/sort: tuplesort.c
> src/backend/commands: analyze.c
>
> Log message:
> Tweak sorting so that nulls appear at the front of a descending sort
> (vs. at the end of a normal sort). This ensures that explicit sorts
> yield the same ordering as a btree index scan. To be really sure that
> that equivalence holds, we use the btree entries in pg_amop to decide
> whether we are looking at a '<' or '>' operator. For a sort operator
> that has no btree association, we put the nulls at the front if the
> operator is named '>' ... pretty grotty, but it does the right thing in
> simple ASC and DESC cases, and at least there's no possibility of getting
> a different answer depending on the plan type chosen.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian - CVS 2001-06-02 19:11:43 pgsql/doc TODO
Previous Message Tom Lane 2001-06-02 19:01:53 pgsql/src include/utils/tuplesort.h backend/ut ...