From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | 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-01-29 13:09:09 |
Message-ID: | eb4d1e15c6822c1937be1491118500dd9201492f.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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?
Yours,
Laurenz Albe
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Document-POSIX-time-zone-sign-oddity-more-visibly.patch | text/x-patch | 3.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Stanley Pagenel | 2025-01-29 14:20:05 | Trying to ugrade from version 16.2 to 17 |
Previous Message | PG Bug reporting form | 2025-01-29 12:24:34 | BUG #18789: logical replication slots are deleted after failovers |