| From: | John Naylor <john(dot)naylor(at)2ndquadrant(dot)com> |
|---|---|
| To: | Artur Zakirov <zaartur(at)gmail(dot)com>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: truncating timestamps on arbitrary intervals |
| Date: | 2020-03-30 12:30:32 |
| Message-ID: | CACPNZCsm-8VaP+QbfHfjRvZ0e3K9zwVM-CTNS4RNC+JH2T-hjg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> I'm going to look into implementing timezone while awaiting comments on v6.
I attempted this in the attached v7. There are 4 new functions for
truncating timestamptz on an interval -- with and without origin, and
with and without time zone.
Parts of it are hackish, and need more work, but I think it's in
passable enough shape to get feedback on. The origin parameter logic
was designed with timestamps-without-time-zone in mind, and
retrofitting time zone on top of that was a bit messy. There might be
bugs.
--
John Naylor https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| v7-datetrunc_interval.patch | application/octet-stream | 24.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2020-03-30 12:43:56 | Re: WAL usage calculation patch |
| Previous Message | Ranier Vilela | 2020-03-30 12:29:51 | Re: Possible copy and past error? (\usr\backend\commands\analyze.c) |