Thread: pgsql: Set the volatility of the timestamptz version of date_bin() back

Set the volatility of the timestamptz version of date_bin() back to immutable

543f36b43d was too hasty in thinking that the volatility of date_bin()
had to match date_trunc(), since only the latter references
session_timezone.

Bump catversion

Per feedback from Aleksander Alekseev
Backpatch to v14, as the former commit was

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/67c33a114f38edbd66f68d7b2c0cb7b03611ec48

Modified Files
--------------
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_proc.dat  | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

John Naylor <john.naylor@postgresql.org> writes:
> Set the volatility of the timestamptz version of date_bin() back to immutable
> 543f36b43d was too hasty in thinking that the volatility of date_bin()
> had to match date_trunc(), since only the latter references
> session_timezone.

> Bump catversion

What you should have done here, at least in the back branch, was *revert*
catversion to what it had been.  As things stand, it would force users of
14beta3 to initdb or pg_upgrade to move to 14.0, for no reason whatsoever.

            regards, tom lane