Re: Inconsistency of timezones in postgresql - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: Inconsistency of timezones in postgresql
Date
Msg-id CAKFQuwb8YSV5m4SkcxrP-xXHN8o9fBMEM6-Qo_0p5x7mN30TLw@mail.gmail.com
Whole thread Raw
In response to Re: Inconsistency of timezones in postgresql  (Chris BSomething <xpusostomos@gmail.com>)
Responses Re: Inconsistency of timezones in postgresql
List pgsql-bugs
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.


David J.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Inconsistency of timezones in postgresql
Next
From: Tim Dysinger
Date:
Subject: Re: BUG #18561: postgresql16-devel rpm cannot be installed due to missing Perl-IPC-Run