| From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | 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 17:50:45 |
| Message-ID: | CAFBsxsFB2OFLgaiwCR-3Tbb3nD16OXMwnqSC+2d_0Ze=p4qm1w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Fri, Sep 3, 2021 at 1:46 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:
>
> On 2021-Sep-03, John Naylor 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.
--
John Naylor
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-09-03 17:56:50 | Re: pgsql: Set the volatility of the timestamptz version of date_bin() back |
| Previous Message | Alvaro Herrera | 2021-09-03 17:45:50 | Re: pgsql: Set the volatility of the timestamptz version of date_bin() back |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-09-03 17:56:16 | Re: prevent immature WAL streaming |
| Previous Message | Andres Freund | 2021-09-03 17:46:46 | Re: prevent immature WAL streaming |