Re: visibility map corruption

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Floris Van Nee <florisvannee(at)optiver(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>
Subject: Re: visibility map corruption
Date: 2021-07-06 22:47:19
Message-ID: 20210706224719.GE26994@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 6, 2021 at 06:30:41PM -0400, Bruce Momjian wrote:
> On Tue, Jul 6, 2021 at 02:27:34PM -0700, Peter Geoghegan wrote:
> > > BTW, is it really necessary for copy_xact_xlog_xid to invoke pg_resetwal
> > > so many times? Why can't we pass all of the update-this options in one
> > > call?
> >
> > No opinion here.
> >
> > > Who's going to do the legwork on this?
> >
> > Can Bruce take care of committing the patch for this? Bruce?
> >
> > This should definitely be in the next point release IMV.
>
> Yes, I can, though it seems like a much bigger issue than pg_upgrade.
> I will be glad to dig into it.

Bertrand Drouvot provided a patch in the thread, so I will start from
that; CC'ing him too.

--
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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2021-07-06 22:49:10 Re: visibility map corruption
Previous Message Peter Geoghegan 2021-07-06 22:46:48 Re: visibility map corruption