Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1r82yG-007y3A-Rm
	for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Nov 2023 18:38:08 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1r82yF-007CWO-Ao
	for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Nov 2023 18:38:07 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1r82v4-007A6F-7u
	for pgsql-hackers@lists.postgresql.org; Tue, 28 Nov 2023 18:34:50 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1r82ux-00929O-Gg
	for pgsql-hackers@postgresql.org; Tue, 28 Nov 2023 18:34:49 +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 3ASIYceo155487;
	Tue, 28 Nov 2023 13:34:38 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Bruce Momjian <bruce@momjian.us>,
        Shay Rojansky <roji@roji.org>,
        pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Missing docs on AT TIME ZONE precedence?
In-reply-to: <eadd117b-7dd0-d1bd-bcd2-a5dedc1fbed5@dunslane.net>
References: <202311271732.hn567fcmvy37@alvherre.pgsql> <4006949.1701117264@sss.pgh.pa.us> <9df52975-686d-c945-36bd-559c930f2dc7@dunslane.net> <4146714.1701185246@sss.pgh.pa.us> <eadd117b-7dd0-d1bd-bcd2-a5dedc1fbed5@dunslane.net>
Comments: In-reply-to Andrew Dunstan <andrew@dunslane.net>
	message dated "Tue, 28 Nov 2023 10:48:00 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <155485.1701196478.1@sss.pgh.pa.us>
Date: Tue, 28 Nov 2023 13:34:38 -0500
Message-ID: <155486.1701196478@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: <https://www.postgresql.org/message-id/155486.1701196478%40sss.pgh.pa.us>
Precedence: bulk

Andrew Dunstan <andrew@dunslane.net> writes:
> On 2023-11-28 Tu 10:27, Tom Lane wrote:
>> OK.  How about rewriting that first para like this?

> LGTM. Thanks.

Thanks for reviewing.  While checking things over one more time,
I noticed that there was an additional violation of this precept,
dating back to long before we understood the hazards: SET is
given its own priority, when it could perfectly well share that
of IDENT.  I adjusted that and pushed.

			regards, tom lane