| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Default to TIMESTAMP WITH TIME ZONE? |
| Date: | 2021-08-12 18:32:49 |
| Message-ID: | 20210812183249.GC4821@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 12, 2021 at 07:24:58PM +0100, Simon Riggs wrote:
> I heard the moan about "Why doesn't TIMESTAMP mean TIMESTAMP WITH TIME
> ZONE" again today, so here is something concrete to address that.
>
> AFAIK, SQL Standard requires the default to be WITHOUT TIME ZONE, but
> nobody seems to think that is useful. We even added a specially
> optimized ALTER TABLE command to make switching from WITHOUT to WITH
> TIME ZONE easy, so it is clearly an important thing to solve.
>
> So add a parameter called
> default_timestamp_with_timezone = off (default) | on
I thought we found that changing behavior via GUC usually ends badly.
--
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 | Tom Lane | 2021-08-12 19:07:47 | Re: Default to TIMESTAMP WITH TIME ZONE? |
| Previous Message | Simon Riggs | 2021-08-12 18:24:58 | Default to TIMESTAMP WITH TIME ZONE? |