Re: truncating timestamps on arbitrary intervals
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: John Naylor <john.naylor@enterprisedb.com>,
Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-04-09T20:02:47Z
Lists: pgsql-hackers
On 30.03.21 18:50, John Naylor wrote: > On Sat, Mar 27, 2021 at 1:06 PM Justin Pryzby <pryzby@telsasoft.com > <mailto:pryzby@telsasoft.com>> wrote: > > > > The current docs seem to be missing a "synopsis", like > > > > +<synopsis> > > +date_trunc(<replaceable>stride</replaceable>, > <replaceable>timestamp</replaceable>, <replaceable>origin</replaceable>) > > +</synopsis> > > The attached > - adds a synopsis > - adds a bit more description to the parameters similar to those in > date_trunc > - documents that negative intervals are treated the same as positive ones > > Note on the last point: This just falls out of the math, so was not > deliberate, but it seems fine to me. We could ban negative intervals, > but that would possibly just inconvenience some people unnecessarily. We > could also treat negative strides differently somehow, but I don't > immediately see a useful and/or intuitive change in behavior to come of > that. committed
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