Re: truncating timestamps on arbitrary intervals

John Naylor <john.naylor@enterprisedb.com>

View thread View on postgr.es

From: John Naylor <john.naylor@enterprisedb.com>

To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>

Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2021-03-30T16:06:33Z

Lists: pgsql-hackers

Attachments

rationalize-future-origin.patch (application/octet-stream) patch

Currently, when the origin is after the input, the result is the timestamp
at the end of the bin, rather than the beginning as expected. The attached
puts the result consistently at the beginning of the bin.

--
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