From: | Tom Lane <tgl(at)hub(dot)org> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql/src include/utils/tuplesort.h backend/ut ... |
Date: | 2001-06-02 19:01:53 |
Message-ID: | 200106021901.f52J1rb34138@hub.org |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-06-02 19:11:17 | Re: pgsql/src include/utils/tuplesort.h backend/ut ... |
Previous Message | Peter Eisentraut - PostgreSQL | 2001-06-02 18:25:19 | pgsql/ /configure /configure.in onfig/programs ... |