From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Default to TIMESTAMP WITH TIME ZONE? |
Date: | 2021-08-13 15:47:49 |
Message-ID: | 20210813154749.GB25560@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Aug 13, 2021 at 07:09:15AM -0700, David G. Johnston wrote:
> On Fri, Aug 13, 2021 at 12:33 AM Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
> wrote:
>
>
> I always use the tz version, except when I forget.
>
>
> I find it nearly impossible for me to forget how this works. But that is
> probably because I just pretend that the standard, multi-word, data types don't
> even exist. It's not that "timestamp" defaults to "WITHOUT TIME ZONE" but
> rather that there are only two types in existence: timestamp and timestamptz.
> It's self-evident which one doesn't handle time zones.
>
>
>
> Suspect that it is extremely rare when one would not want to use the TZ
> option, which suggests to me that using TZ should be the default.
>
>
>
> I would agree, but at this point I'd leave it up to documentation and
> educational materials to teach/encourage, not runtime behaviors.
Yes, only using 'timetamptz' does fix it.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2021-08-13 15:59:40 | Re: pgsql: pgstat: Bring up pgstat in BaseInit() to fix uninitialized use o |
Previous Message | Adrian Klaver | 2021-08-13 15:34:56 | Re: Multiple Postgres process are running in background |