| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, John Naylor <john(dot)naylor(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Set the volatility of the timestamptz version of date_bin() back |
| Date: | 2021-09-03 20:47:54 |
| Message-ID: | 2598498.1630702074@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2021-Sep-03, John Naylor wrote:
>> On Fri, Sep 3, 2021 at 1:46 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-09-04 01:05:09 | pgsql: Remove arbitrary MAXPGPATH limit on command lengths in pg_ctl. |
| Previous Message | Tom Lane | 2021-09-03 20:42:58 | Re: pgsql: Set the volatility of the timestamptz version of date_bin() back |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Zhang | 2021-09-03 20:54:25 | Re: ORDER BY pushdowns seem broken in postgres_fdw |
| Previous Message | Tom Lane | 2021-09-03 20:42:58 | Re: pgsql: Set the volatility of the timestamptz version of date_bin() back |