| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Chris BSomething <xpusostomos(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Inconsistency of timezones in postgresql |
| Date: | 2024-08-01 01:58:15 |
| Message-ID: | CAKFQuwb8YSV5m4SkcxrP-xXHN8o9fBMEM6-Qo_0p5x7mN30TLw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wednesday, July 31, 2024, Chris BSomething <xpusostomos(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Dysinger | 2024-08-01 02:04:21 | Re: BUG #18561: postgresql16-devel rpm cannot be installed due to missing Perl-IPC-Run |
| Previous Message | David G. Johnston | 2024-08-01 01:51:31 | Re: Inconsistency of timezones in postgresql |