| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: to_timestamp TZH and TZM format specifiers |
| Date: | 2018-01-03 19:54:45 |
| Message-ID: | 23740.1515009285@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> writes:
> On 01/03/2018 08:39 PM, Tom Lane wrote:
>> Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> writes:
>>> Shouldn't this support TZS or something for seconds?
>> According to the docs I cited upthread, there's no such field type
>> in Oracle.
> So what?
Well, the function is meant to be Oracle-compatible, so where's the
use case?
I'm pretty sure that it's been years since any standard time zones
weren't an integral number of minutes off UTC, which may explain
why Oracle hasn't felt the need for this. I notice that the SQL
standard itself also believes that timezone offsets must be an
integral number of minutes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2018-01-03 20:06:59 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |
| Previous Message | Tomas Vondra | 2018-01-03 19:53:59 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |