| From: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andreas Karlsson <andreas(at)proxel(dot)se> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: date_trunc() in a specific time zone |
| Date: | 2018-10-29 15:40:24 |
| Message-ID: | 21dec999-c2b7-db9e-7f68-899436a5f2a3@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 29/10/2018 16:36, Tom Lane wrote:
> Andreas Karlsson <andreas(at)proxel(dot)se> writes:
>> Hm, I am not sure if I see any major win from writing
>> date_trunc('day', timestamptz '2001-02-16 20:38:40+00', 'Australia/Sydney')
>> instead of
>> date_trunc('day', timestamptz '2001-02-16 20:38:40+00' AT TIME ZONE
>> 'Australia/Sydney')
>
> The latter would give you timestamp without time zone, whereas I think
> what Vik wants is timestamp with time zone. Yeah, you could then convert
> it back with a second application of AT TIME ZONE 'Australia/Sydney',
> but that's both inefficient
Hmm, converting it back is exactly what my function does...
> and mighty confusing.
This is my justification for needing the patch.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2018-10-29 15:43:40 | Re: date_trunc() in a specific time zone |
| Previous Message | Tom Lane | 2018-10-29 15:36:32 | Re: date_trunc() in a specific time zone |