| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru> |
| Subject: | Re: to_timestamp TZH and TZM format specifiers |
| Date: | 2018-01-03 19:27:55 |
| Message-ID: | 22520.1515007675@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> On 01/03/2018 01:34 PM, Tom Lane wrote:
>> BTW, I had not known this before, but according to the page I'm
>> looking at
>> https://docs.oracle.com/database/121/SQLRF/sql_elements004.htm#SQLRF00212
>> Oracle also supports "TZD" to mean a time zone abbreviation (their
>> example is "PDT") and "TZR" to mean a time zone name (their example
>> is "US/Pacific", so yes they mean the IANA zone names). Those seem
>> remarkably useful, so I'm surprised we've not added support for them.
> I also agree that TZD and TZR would be very useful, but perhaps they
> could be done in a separate patch.
Yes, of course, I did not mean to imply that this patch needs to include
them. I was just surprised because I'd always believed there was no such
facility in Oracle. I wonder how long ago they added those ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-01-03 19:31:44 | Re: Better testing coverage and unified coding for plpgsql loops |
| Previous Message | Andrew Dunstan | 2018-01-03 19:21:51 | Re: to_timestamp TZH and TZM format specifiers |