pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: John Naylor <john.naylor@enterprisedb.com>
Cc: John Naylor <john.naylor@postgresql.org>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: pgsql: Set the volatility of the timestamptz version of date_bin() back
Date: Fri, 03 Sep 2021 16:47:54 -0400
Message-ID: <2598498.1630702074@sss.pgh.pa.us> (raw)
In-Reply-To: <202109031756.d6li4szj5zje@alvherre.pgsql>
References: <202109031756.d6li4szj5zje@alvherre.pgsql>

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2021-Sep-03, John Naylor wrote:
>> On Fri, Sep 3, 2021 at 1:46 PM Alvaro Herrera <alvherre@alvh.no-ip.org>
>> wrote:
>>> 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?

>> This was for correcting a mistake (although the first commit turned out to
>> be a mistake itself), so I understood it to be necessary.

> A crazy idea might have been to return to the original value.

Yes, that is what should have been done, as I complained over
in pgsql-committers before seeing this exchange.  As things
stand, a pg_upgrade is going to be forced on beta3 users
without even the excuse of fixing a bug.

			regards, tom lane





view thread (8+ messages)

Message-ID: <2598498.1630702074@sss.pgh.pa.us>
Permalink:  ../2598498.1630702074@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2598498.1630702074@sss.pgh.pa.us

 · 

reply

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, alvherre@alvh.no-ip.org, john.naylor@enterprisedb.com, 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: <2598498.1630702074@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