Re: Recent updates - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Recent updates
Date
Msg-id 199807151704.NAA13760@candle.pha.pa.us
Whole thread Raw
In response to Re: Recent updates  ("Thomas G. Lockhart" <lockhart@alumnus.caltech.edu>)
List pgsql-hackers
> > > > What does 'select null order by 1;' do now?
> > you can do a NULL test there and prevent oper() from even being
> > called.
>
> postgres=> select null order by 1;
> ?column?
> --------
>
> (1 row)
>
> There are three or four cases in transformSortClause() and I had fixed
> only one case for UNION. A second case is now fixed, in the same way; I
> assigned INT4OID to the column type for the "won't actually happen"
> sort. Didn't want to skip the code entirely, since the backend needs to
> _try_ a sort to get the NULLs right. I'm not certain under what
> circumstances the other cases are invoked; will try some more testing...
>
> Off to work now :)

Good.  Yes, I agree we need to put something in that place.

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: Recent updates
Next
From: Vadim Mikheev
Date:
Subject: Re: AW: [HACKERS] "internal error" triggered by EXISTS()