2026-02-26 release announcement draft
Hi,
Please see the draft of the 2026-02-26 release announcement. Please
review for inaccuracies.
For the additional steps related to the `json[b]_strip_nulls()` issue, I
primarily borrowed from the guidance in the release notes. For users who
already updated to PG < 18.3, I didn't think it'd be worthwhile to say
they should `pg_upgrade` to 18.3, given the post-update steps would be
much less disruptive. However, I'm open to other suggestions for how to
frame the guidance.
Thanks,
Jonathan
Attachments:
20260226updaterelease.mdtext/plain; charset=UTF-8; name=20260226updaterelease.mdDownload
Hi,
You should also execute this command in the `template0` and `template1` databases so future databases you create in your PostgreSQL cluster have the correct function volatility setting.
Shouldn't it be mentioned that template0 is read only and give instructions how to do this properly?
Regards
Daniel
On 2/23/26 1:58 AM, Daniel Westermann (DWE) wrote:
Hi,
You should also execute this command in the `template0` and `template1` databases so future databases you create in your PostgreSQL cluster have the correct function volatility setting.
Shouldn't it be mentioned that template0 is read only and give instructions how to do this properly?
"template0" isn't read-only; it isn't connectable by default. That said,
this is a good recommendation given the behaviors of these databases. I
modified the text to include a link to the documentation for more
information on the core template databases. Please see attached.
Thanks,
Jonathan
Attachments:
20260226updaterelease.mdtext/plain; charset=UTF-8; name=20260226updaterelease.mdDownload
You should also execute this command in the `template0` and `template1` databases so future databases you create in your PostgreSQL cluster have >the correct function volatility setting.
Shouldn't it be mentioned that template0 is read only and give instructions how to do this properly?
"template0" isn't read-only; it isn't connectable by default. That said,
this is a good recommendation given the behaviors of these databases. I
modified the text to include a link to the documentation for more
information on the core template databases. Please see attached.
Ah, yes, correct. Looks good, thank you.
Regards
Daniel