| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)postgresql(dot)org> |
| Cc: | pgsql-committers(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:42:58 |
| Message-ID: | 2598260.1630701778@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
John Naylor <john(dot)naylor(at)postgresql(dot)org> writes:
> 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
What you should have done here, at least in the back branch, was *revert*
catversion to what it had been. As things stand, it would force users of
14beta3 to initdb or pg_upgrade to move to 14.0, for no reason whatsoever.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-09-03 20:47:54 | Re: pgsql: Set the volatility of the timestamptz version of date_bin() back |
| Previous Message | Tom Lane | 2021-09-03 20:39:59 | pgsql: Disallow creating an ICU collation if the DB encoding won't supp |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-09-03 20:47:54 | Re: pgsql: Set the volatility of the timestamptz version of date_bin() back |
| Previous Message | Andres Freund | 2021-09-03 20:20:59 | Re: Estimating HugePages Requirements? |