| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "rihad" <rihad(at)mail(dot)ru>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: any way for ORDER BY x to imply NULLS FIRST in 8.3? |
| Date: | 2007-11-07 19:05:23 |
| Message-ID: | 87640dx4ek.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
>> Perhaps we can have a parameter?
>> default_null_sorting = 'last' # may alternatively be set to 'first'
>
> Not unless it's locked down at initdb time. Otherwise flipping the
> value bars you from using every existing index ... including those
> on the system catalogs ... which were made with the other setting.
Surely if we added this we would also add explicit NULLS LAST clauses to all
system catalog indexes and system views and make explicitly constructed scans
in the backend use NULLS LAST.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Kovalevski | 2007-11-07 19:11:29 | Re: odbcng |
| Previous Message | Alvaro Herrera | 2007-11-07 18:41:50 | Re: The .pgpass file |