On Thu, May 13, 2021 at 09:01:41PM -0500, Justin Pryzby wrote:
> On Mon, May 10, 2021 at 09:40:45AM -0500, Justin Pryzby wrote:
> > Should any of these be included?
>
> New SQL-accessible functionality should be included:
> > 8c15a29745 Allow ALTER TYPE to update an existing type's typsubscript value.
OK, text is:
<listitem>
<!--
Author: Tom Lane <t...@sss.pgh.pa.us>
2020-12-11 [8c15a2974] Allow ALTER TYPE to update an existing type's
typsubscri
-->
<para>
Allow ALTER TYPE to specify or remove a SUBSCRIPT handler
(Tom Lane)
</para>
</listitem>
> I'm undecided on this one:
> > 7db0cd2145 Set PD_ALL_VISIBLE and visibility map bits in COPY FREEZE
>
> People who didn't used to use FREEZE (because it didn't work or otherwise)
> might want to start using it.
Yes, that seems very important:
<listitem>
<!--
Author: Tomas Vondra <tomas.von...@postgresql.org>
2021-01-17 [7db0cd214] Set PD_ALL_VISIBLE and visibility map bits in
COPY FREEZ
-->
<para>
Have COPY FREEZE appropriately update page visibility bits
(Anastasia Lubennikova, Pavan Deolasee, Jeff Janes)
</para>
</listitem>
This one one of those, "I must be confused, since we certainly already
did this before."
> I'm withdrawing these, as modifications to existing log messages don't need to
> be included:
>
> > 10a5b35a00 Report resource usage at the end of recovery
> > 7e453634bb Add additional information in the vacuum error context.
> > 1ea396362b Improve logging of bad parameter values in BIND messages.
OK.
--
Bruce Momjian <br...@momjian.us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
