Horton

Re: Inconsistency of timezones in postgresql

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Aleksander Alekseev <aleksander@timescale.com>, pgsql-bugs@lists.postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>, Chris BSomething <xpusostomos@gmail.com>
Date: 2025-02-18T20:52:08Z
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

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@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.