From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: John Naylor <john.naylor@postgresql.org>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: Set the volatility of the timestamptz version of date_bin() back
Date: Fri, 3 Sep 2021 13:45:50 -0400
Message-ID: <202109031745.2ukvwzuigtwk@alvherre.pgsql> (raw)
In-Reply-To: <E1mMDCu-0008Pf-Dv@gemulon.postgresql.org>
On 2021-Sep-03, John Naylor wrote:
> 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
These catversion bumps in branch 14 this late in the cycle seem suspect.
Didn't we have some hesitation to push multirange unnest around beta2
precisely because of a desire to avoid catversion bumps?
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
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: alvherre@alvh.no-ip.org, john.naylor@postgresql.org, pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: Set the volatility of the timestamptz version of date_bin() back
In-Reply-To: <202109031745.2ukvwzuigtwk@alvherre.pgsql>
* 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