Re: truncating timestamps on arbitrary intervals
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: John Naylor <john.naylor@enterprisedb.com>, pgsql-hackers@postgresql.org
Date: 2021-03-27T17:06:11Z
Lists: pgsql-hackers
On Wed, Mar 24, 2021 at 08:50:59PM +0100, Peter Eisentraut wrote:
> On 24.03.21 18:58, John Naylor wrote:
> > > 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?
>
> right, plus some documentation adjustments perhaps
+1
The current docs seem to be missing a "synopsis", like
+<synopsis>
+date_trunc(<replaceable>stride</replaceable>, <replaceable>timestamp</replaceable>, <replaceable>origin</replaceable>)
+</synopsis>
--
Justin
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