Re: truncating timestamps on arbitrary intervals
John Naylor <john.naylor@enterprisedb.com>
From: John Naylor <john.naylor@enterprisedb.com>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-03-24T17:58:09Z
Lists: pgsql-hackers
On Wed, Mar 24, 2021 at 11:38 AM Peter Eisentraut <
peter.eisentraut@enterprisedb.com> wrote:
> Committed.
>
> I noticed that some of the documentation disappeared between v9 and v10.
> So I put that back and updated it appropriately. I also added a few
> more test cases to cover some things that have been discussed during the
> course of this thread.
Thanks! I put off updating the documentation in case the latest approach
was not feature-rich enough.
> As a potential follow-up, should we perhaps add named arguments? That
> might make the invocations easier to read, depending on taste.
I think it's quite possible some users will prefer that. All we need is to
add something like
proargnames => '{bin_width,input,origin}'
to the catalog, right?
Also, I noticed that I put in double semicolons in the new functions
somehow. I'll fix that as well.
--
John Naylor
EDB: http://www.enterprisedb.com
Commits
-
Disallow negative strides in date_bin()
- fc0d9b8c224f 14.0 landed
- 3ba70d4e1523 15.0 landed
-
Improve behavior of date_bin with origin in the future
- 496e58bb0e5e 14.0 landed
-
doc: Additional documentation for date_bin
- 49fb4e6b2490 14.0 landed
-
Add date_bin function
- 49ab61f0bdc9 14.0 landed