On Sat, Jul  2, 2022 at 08:13:41PM -0400, Bruce Momjian wrote:
> On Fri, Jul  1, 2022 at 09:56:17AM -0700, Peter Geoghegan wrote:
> > On Fri, Jul 1, 2022 at 9:41 AM Bruce Momjian <br...@momjian.us> wrote:
> > > > It might be worth explaining the shift directly in the release notes.
> > > > The new approach is simpler and makes a lot more sense -- why should
> > > > the relfrozenxid be closely tied to freezing? We don't necessarily
> > >
> > > I don't think this is an appropriate detail for the release notes.
> > 
> > Okay. What about saying something about relminmxid advancement where
> > the database consumes lots of multixacts?
> 
> No. same issue.

Actually, I was wrong.  I thought that we only mentioned that we
computed a more agressive xid, but now see I was mentioning the _frozen_
xid.  Reading the commit, we do compute the multi-xid and store that too
so I have updated the PG 15 release notes with the attached patch.

-- 
  Bruce Momjian  <br...@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson

diff --git a/doc/src/sgml/release-15.sgml b/doc/src/sgml/release-15.sgml
index 47ac329e79..179ad37d9d 100644
--- a/doc/src/sgml/release-15.sgml
+++ b/doc/src/sgml/release-15.sgml
@@ -994,7 +994,8 @@ Author: Peter Geoghegan <p...@bowt.ie>
       <listitem>
        <para>
         Allow <link linkend="routine-vacuuming">vacuum</link> to be more
-        aggressive in setting the oldest frozenxid (Peter Geoghegan)
+        aggressive in setting the oldest frozen and multi transaction id
+        (Peter Geoghegan)
        </para>
       </listitem>
 

Reply via email to