Re: date_trunc() in a specific time zone
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Paul A Jungwirth <pj@illuminatedcomputing.com>
Cc: vik.fearing@2ndquadrant.com,
Steve Crawford <scrawford@pinpointresearch.com>, andreas@proxel.se,
pgsql-hackers@lists.postgresql.org
Date: 2018-10-29T18:46:15Z
Lists: pgsql-hackers
Paul A Jungwirth <pj@illuminatedcomputing.com> writes: > I guess the issue is that for w/o-tz, you need an extra parameter to > say what you're assuming you started with. Yeah, that's basically what I was wondering. I suppose we could imagine a 4-argument function to cover that case, but I do not think it's worth the trouble, given that there are other ways to do it. BTW, I'd been hoping that we could avoid rotate-to-local-and-back in Vik's desired case, but after further thought I suspect the only real optimization that's possible compared to writing it out with two AT TIME ZONE constructs is to do the zone name lookup just once. As an example, truncating to a day-or-larger boundary could result in shifting to a different UTC offset than you started with, due to crossing a DST boundary. regards, tom lane
Commits
-
Add a timezone-specific variant of date_trunc().
- 600b04d6b5ef 12.0 landed