From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Jan Wieck <jan(at)wi3ck(dot)info> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Alexander Shutyaev <shutyaev(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade and wraparound |
Date: | 2021-04-30 19:32:54 |
Message-ID: | 20210430193254.GA5370@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Mar 13, 2021 at 08:43:54AM -0500, Jan Wieck wrote:
> On 3/12/21 8:30 PM, Michael Paquier wrote:
> > Hi Jan,
> >
> > On Fri, Mar 12, 2021 at 06:13:33PM -0500, Jan Wieck wrote:
> > > One of the things in my way is that when using pg_resetwal to put the
> > > NextXID way into the future (to push the old cluster close to wraparound for
> > > example), the postmaster won't start because it doesn't have the pg_xact
> > > files for that around. Should pg_resetwal create the files in the gap
> > > between the old NextXID and the new one?
> >
> > I think that you should add this patch to the next commit fest to
> > track it properly:
> > https://commitfest.postgresql.org/33/
> > --
> > Michael
> >
>
> Actually this is the wrong patch (this one is for PG-12, not for HEAD). Will
> update later today.
>
> But yes, putting it into the next commitfest after initial discussion is the
> plan.
Uh, were either of these things done?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Beachy | 2021-04-30 20:53:52 | Re: -1/0 virtualtransaction |
Previous Message | Tom Lane | 2021-04-30 14:29:12 | Re: "Skipping" BitmapHeapScan for simple counts |