Horton

Re: Inconsistency of timezones in postgresql

Laurenz Albe <laurenz.albe@cybertec.at>

View thread
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Aleksander Alekseev <aleksander@timescale.com>, pgsql-bugs@lists.postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Chris BSomething <xpusostomos@gmail.com>
Date: 2025-01-29T13:09:09Z
Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. doc: add example of sign mismatch with POSIX/ISO-8601 time zones

Attachments

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