Re: Inconsistency of timezones in postgresql
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Chris BSomething <xpusostomos@gmail.com>
Cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2024-08-01T01:51:31Z
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 →
-
doc: add example of sign mismatch with POSIX/ISO-8601 time zones
- 06dc1ffd2409 18.0 landed
On Wednesday, July 31, 2024, Chris BSomething <xpusostomos@gmail.com> wrote: > > Riddle me this... I have a field of type timestamp. I do 3 queries on a > particular record one is AT TIME ZONE 'UTC', ones is AT TIME ZONE > Australia/Sydney, one is plain, without a clause and I get: > > > We are no longer in bug reporting territory. Depesz wrote a good article on all this a while back. I’d suggest reading it then following up further on the -general mailing list if you still have questions. https://www.depesz.com/2014/04/04/how-to-deal-with-timestamps/ David J.