| From: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | vik(dot)fearing(at)2ndquadrant(dot)com, Steve Crawford <scrawford(at)pinpointresearch(dot)com>, andreas(at)proxel(dot)se, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: date_trunc() in a specific time zone |
| Date: | 2018-10-29 17:13:10 |
| Message-ID: | CA+renyUoD6j+CWmttZ9q1CaUMd7JCA0oXw2eTja4GfT0mZWQLg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 29, 2018 at 9:58 AM Paul A Jungwirth
<pj(at)illuminatedcomputing(dot)com> wrote:
> This patch adds a 3-arg version for date_trunc(text, timestamptz,
> text). I'm saying it would be nice to also have a 3-arg version for
> date_trunc(text, timestamp, text). It would do the same thing, except
> take a timestamp w/o tz and return a timestamp w/o tz.
Thinking about this some more, perhaps the timestamp-to-timestamp
version would depend on assumptions that aren't always valid. In my
world the server timezone is always UTC, and the database clients
always convert values to UTC before saving. But if those assumptions
don't hold the simple implementation of 2x AT TIME ZONE might not work
correctly. I can try it out and see....
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul A Jungwirth | 2018-10-29 17:29:37 | Re: date_trunc() in a specific time zone |
| Previous Message | Paul A Jungwirth | 2018-10-29 16:58:58 | Re: date_trunc() in a specific time zone |