| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com>, pgsql-sql <pgsql-sql(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Global setting for ORDER BY ... NULLS FIRST / LAST |
| Date: | 2022-03-01 15:02:26 |
| Message-ID: | 2837300.1646146946@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Tue, Mar 1, 2022 at 7:16 AM Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com>
> wrote:
>> Is there a global PostgreSQL server setting or SQL session parameter that
>> defines the default for ORDER BY ... NULLS FIRST / LAST ?
> IMO, not enough of a benefit to spend development time on. Having global
> configuration like this is something that should be, and in general is,
> avoided. Most of the exceptions to this have been regretted.
Yeah. We have generally found that settings that change query semantics
are a net evil.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | asalias mark | 2022-03-01 17:55:36 | pg_stat_progress_copy not working as intended |
| Previous Message | David G. Johnston | 2022-03-01 14:41:48 | Re: Global setting for ORDER BY ... NULLS FIRST / LAST |