pgsql: Improve behavior of date_bin with origin in the future - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Improve behavior of date_bin with origin in the future
Date
Msg-id E1lVHfX-0002sR-TP@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Improve behavior of date_bin with origin in the future

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.  This puts the result consistently at the beginning of the
bin.

Author: John Naylor <john.naylor@enterprisedb.com>
Discussion: https://www.postgresql.org/message-id/CAFBsxsGjLDxQofRfH+d4KSAXxPf3MMevUG7s6EDfdBOvHLDLjw@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/496e58bb0e5e939e6ed5839c92b05e3ab11b54bb

Modified Files
--------------
src/backend/utils/adt/timestamp.c       | 14 +++++++++
src/test/regress/expected/timestamp.out | 54 +++++++++++++++++++++++++++++++++
src/test/regress/sql/timestamp.sql      | 34 +++++++++++++++++++++
3 files changed, 102 insertions(+)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix failure of xlogprefetch.h to include all prerequisite header
Next
From: Noah Misch
Date:
Subject: pgsql: Standardize pg_authid oid_symbol values.