From: | "Thomas G(dot) Lockhart" <lockhart(at)alumnus(dot)caltech(dot)edu> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: Recent updates |
Date: | 1998-07-15 17:06:42 |
Message-ID: | 35ACE1A2.6BE91491@apop-server.alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 :)
- Tom
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Mikheev | 1998-07-15 17:53:41 | Re: AW: [HACKERS] "internal error" triggered by EXISTS() |
Previous Message | Bruce Momjian | 1998-07-15 17:04:21 | Re: Recent updates |