| From: | John Naylor <john(dot)naylor(at)2ndquadrant(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: truncating timestamps on arbitrary intervals |
| Date: | 2020-06-30 04:34:22 |
| Message-ID: | CACPNZCvV5y_ZZC4BEZtRdGOdzYKw9WZqc_cGYoJsGFSuL8HeTw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
In v9, I've simplified the patch somewhat to make it easier for future
work to build on.
- When truncating on month-or-greater intervals, require the origin to
align on month. This removes the need to handle weird corner cases
that have no straightforward behavior.
- Remove hackish and possibly broken code to allow origin to be after
the input timestamp. The default origin is Jan 1, 1 AD, so only AD
dates will behave correctly by default. This is not enforced for now,
since it may be desirable to find a way to get this to work in a nicer
way.
- Rebase docs over PG13 formatting changes.
--
John Naylor https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| v9-datetrunc-interval.patch | application/octet-stream | 28.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-06-30 04:41:14 | Re: A patch for get origin from commit_ts. |
| Previous Message | David Rowley | 2020-06-30 04:24:00 | Re: Use of "long" in incremental sort code |