Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nP41J-0006tD-Hp for pgsql-sql@arkaria.postgresql.org; Tue, 01 Mar 2022 15:02:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nP41I-0006L2-Ey for pgsql-sql@arkaria.postgresql.org; Tue, 01 Mar 2022 15:02:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nP41I-0006K8-5u for pgsql-sql@lists.postgresql.org; Tue, 01 Mar 2022 15:02:32 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nP41F-0006OI-UF for pgsql-sql@lists.postgresql.org; Tue, 01 Mar 2022 15:02:31 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 221F2QiO2837301; Tue, 1 Mar 2022 10:02:26 -0500 From: Tom Lane To: "David G. Johnston" cc: Sebastien Flaesch , pgsql-sql Subject: Re: Global setting for ORDER BY ... NULLS FIRST / LAST In-reply-to: References: Comments: In-reply-to "David G. Johnston" message dated "Tue, 01 Mar 2022 07:41:48 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2837299.1646146946.1@sss.pgh.pa.us> Date: Tue, 01 Mar 2022 10:02:26 -0500 Message-ID: <2837300.1646146946@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > On Tue, Mar 1, 2022 at 7:16 AM Sebastien Flaesch > 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