| 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-07 01:49:03 |
| Message-ID: | 20210707014903.GH26994@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 6, 2021 at 08:36:13PM -0400, Bruce Momjian wrote:
> On Tue, Jul 6, 2021 at 06:49:10PM -0400, Bruce Momjian wrote:
> > My point is that there are a lot internals involved here that are not
> > part of pg_upgrade, though it probably only affects pg_upgrade. Anyway,
> > Bertrand patch seems to have what I need.
>
> One question is how do we want to handle cases where -x next_xid is used
> but -u oldestXid is not used? Compute a value for oldestXid like we did
> previously? Throw an error? Leave oldestXid unchanged? I am thinking
> the last option.
Here is a modified version of Bertrand's patch, with docs, that does the
last option.
--
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.
| Attachment | Content-Type | Size |
|---|---|---|
| oldestxid.diff.gz | application/gzip | 3.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2021-07-07 02:01:07 | Slightly improve initdb --sync-only option's help message |
| Previous Message | David Rowley | 2021-07-07 01:20:24 | Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series) |