| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)postgresql(dot)org> |
| Cc: | 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:45:50 |
| Message-ID: | 202109031745.2ukvwzuigtwk@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2021-09-03 17:50:45 | Re: pgsql: Set the volatility of the timestamptz version of date_bin() back |
| Previous Message | John Naylor | 2021-09-03 17:42:28 | pgsql: Set the volatility of the timestamptz version of date_bin() back |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bossart, Nathan | 2021-09-03 17:46:05 | Re: Estimating HugePages Requirements? |
| Previous Message | John Naylor | 2021-09-03 17:42:28 | pgsql: Set the volatility of the timestamptz version of date_bin() back |