From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | pg(at)bowt(dot)ie |
Cc: | lucas(dot)valardao(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data |
Date: | 2021-01-29 07:14:09 |
Message-ID: | 20210129.161409.1144489495586105660.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
At Thu, 28 Jan 2021 18:53:18 -0800, Peter Geoghegan <pg(at)bowt(dot)ie> wrote in
> On Thu, Jan 28, 2021 at 6:40 PM Kyotaro Horiguchi
> <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> > Otherwise..., the last choice is inspecting the cluster in
> > binary-level to infer the relation map then create the file from
> > scratch... Almost impossible.
>
> pg_hexedit includes a tool that can output the contents of a
> pg_filenode.map file. It wouldn't be that hard to put one together if
> you were extremely motivated.
Oops! That was a trap robbed my time. A rush work is attached.
> However, even that probably would not be enough. I don't see any
> reason to imagine that that's the only file that's corrupt.
Agreed. I don't beleve the file is the only one that has been broken.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
Attachment | Content-Type | Size |
---|---|---|
filenodemap_hexedit.tar.gz | application/octet-stream | 6.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | GMX Steffen | 2021-01-29 13:23:31 | Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed |
Previous Message | Peter Geoghegan | 2021-01-29 02:53:18 | Re: BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data |