Horton

Re: Inconsistency of timezones in postgresql

David G. Johnston <david.g.johnston@gmail.com>

View thread
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:58:15Z
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 Wednesday, July 31, 2024, Chris BSomething <xpusostomos@gmail.com> wrote:

>
> Is it wrong to assign current_timestamp to a timestamp field because
> current_timestamp is "with time zone"? If so, that's amazing since I
> thought under the hood its all UTC.  I can't see that mentioned in the
> documentation that using current_timestamp can be so dangerously wrong when
> assigned to a timestamp.
>

Using timestamp without time zone is really the issue here.  There is even
a “don’t do this” entry for it.


https://wiki.postgresql.org/wiki/Don%27t_Do_This#Don.27t_use_timestamp_.28without_time_zone.29_to_store_UTC_times

David J.