From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Naylor <john.naylor@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Set the volatility of the timestamptz version of date_bin() back
Date: Fri, 03 Sep 2021 16:42:58 -0400
Message-ID: <2598260.1630701778@sss.pgh.pa.us> (raw)
In-Reply-To: <E1mMDCu-0008Pf-Dv@gemulon.postgresql.org>
References: <E1mMDCu-0008Pf-Dv@gemulon.postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, john.naylor@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Set the volatility of the timestamptz version of date_bin() back
In-Reply-To: <2598260.1630701778@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox