| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: date_trunc() in a specific time zone |
| Date: | 2018-10-29 23:18:41 |
| Message-ID: | 1fae95e1-af93-d625-ee63-b08392454b11@proxel.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/29/2018 04:36 PM, 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 and mighty confusing.
Sloppy reading on my part, thanks for pointing it out.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2018-10-29 23:25:47 | Re: date_trunc() in a specific time zone |
| Previous Message | Andreas 'ads' Scherbaum | 2018-10-29 23:08:49 | Installation instructions update (pg_ctl) |