From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Chris BSomething <xpusostomos(at)gmail(dot)com> |
Subject: | Re: Inconsistency of timezones in postgresql |
Date: | 2025-02-18 20:52:08 |
Message-ID: | Z7Ty-H06PTZr-pgK@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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 <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-02-18 22:24:06 | Re: BUG #18815: Logical replication worker Segmentation fault |
Previous Message | Tom Lane | 2025-02-18 20:38:34 | Re: BUG #18815: Logical replication worker Segmentation fault |