| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Default to TIMESTAMP WITH TIME ZONE? |
| Date: | 2021-08-12 18:24:58 |
| Message-ID: | CANbhV-G-n4bFmdzaOwiaq8pyDgyFod84dWd34N0QQzEJR0RCyA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
Thoughts?
--
Simon Riggs http://www.EnterpriseDB.com/
| Attachment | Content-Type | Size |
|---|---|---|
| default_timestamp_with_timezone.v1.patch | application/octet-stream | 3.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2021-08-12 18:32:49 | Re: Default to TIMESTAMP WITH TIME ZONE? |
| Previous Message | John Naylor | 2021-08-12 18:16:25 | Re: badly calculated width of emoji in psql |