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 ) id 1tkUZi-004Ufj-4s for pgsql-bugs@arkaria.postgresql.org; Tue, 18 Feb 2025 20:52:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tkUZg-000lM4-Mp for pgsql-bugs@arkaria.postgresql.org; Tue, 18 Feb 2025 20:52:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tkUZg-000lLp-Eo for pgsql-bugs@lists.postgresql.org; Tue, 18 Feb 2025 20:52:12 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tkUZe-001aO0-3D for pgsql-bugs@lists.postgresql.org; Tue, 18 Feb 2025 20:52:11 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=uk4Uj3d1CQ/xQ806ZsT/nuRneiyPZRks9ixWQVX2KMs=; b=LqGOHihy6M40YKrnm98529AU6/ FMQ1pY20ub3TvPSbyMUz0GyyDJeSSu/XqAvgcReqK7ooACowZ3AukltJfjWRY6pcFB9q1H7dmEr23 Y/wdqEL5HZ72lowQtprbhjFaScuRzjH8zvKD9zNMGov+GWvl13FtA1rwp/G/6ul1sY9ws8djoGp0d 4TBl4cDqlosggtIKMflBdLI4+vO2lSJ09HW+/V2ZwH1RhXEwS4X6Q5FZPbQ1mc8ayaGmrVlQxh5Zy lp0+TxCN7XgTLQJ10zAg6/UuWTGqVk0GX8bdVAV+SyjikaOUeZ0zMyY/RQZykAxhTuWbZO/BC0wQd cznHSeZw==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1tkUZc-008Wrv-19; Tue, 18 Feb 2025 15:52:08 -0500 Date: Tue, 18 Feb 2025 15:52:08 -0500 From: Bruce Momjian To: Laurenz Albe Cc: Aleksander Alekseev , pgsql-bugs@lists.postgresql.org, Tom Lane , Chris BSomething Subject: Re: Inconsistency of timezones in postgresql Message-ID: References: <3384710.1722438948@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Jan 29, 2025 at 02:09:09PM +0100, Laurenz Albe wrote: > On Thu, 2024-08-01 at 13:24 +0300, Aleksander Alekseev wrote: > > > I think this is a documentation issue, specifically that Section 8.5.3 > > > is not sufficiently in-your-face about "UTC+2" not meaning what you > > > probably think.  We didn't really do anybody any favors by shoving > > > those details off to Appendix B. > > > > IMO the warning should be placed closer to the documentation for AT > > TIME ZONE where users have more chances to find it. Here is the patch. > > I think it is odd to have a second set of examples in the documentation > of AT TIME ZONE. My attached patch instead adds an example with > explanation to the already existing examples and a nore to the data > types section. > > What do you think? Thanks, patch applied to master. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.