Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed - Mailing list pgsql-general

From Michael Paquier
Subject Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed
Date
Msg-id CAB7nPqRT56Pr9d-z3d_gSUX5+HF6qZHxuW1TbKnLyQtSM_2r2A@mail.gmail.com
Whole thread Raw
In response to Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed  (Tatsuki Kadomoto <tatsuki.kadomoto@proceranetworks.com>)
List pgsql-general
On Fri, Aug 26, 2016 at 9:09 AM, Tatsuki Kadomoto
<tatsuki.kadomoto@proceranetworks.com> wrote:
> Does Postgre have any mechanism to correct the mapping file automatically?

When the relation mapping changes, the file gets rewritten at
transaction commit. I guess that the error you saw previously (be
careful, that's a corruption!) got clobbered afterwards.
--
Michael


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Understanding Postgres Memory Usage
Next
From: John R Pierce
Date:
Subject: Re: LOG: could not fork new process for connection: Cannot allocate memory