Postgres Pro
Downloads
Home   >   mailing lists

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 CAB7nPqRSFx974uQPnqUSDcBh75nQ7bwrsbmf-MBXnCs3nFr_tQ@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>)
Responses Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed  (Tatsuki Kadomoto <tatsuki.kadomoto@proceranetworks.com>)
List pgsql-general
Tree view 
On Thu, Aug 25, 2016 at 9:48 PM, Tatsuki Kadomoto
<tatsuki.kadomoto@proceranetworks.com> wrote:
> Does this mean it's a kind of expected to face checksum error when the mapping file is relocated by VACUUM FULL?
> I faced the checksum error exactly when VACUUM FULL was running and it has never been detected until now.

No, it's not. This should not happen. And this means that your data
folder is facing some corruption.
--
Michael

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: LOG: could not fork new process for connection: Cannot allocate memory
Next
From: Tatsuki Kadomoto
Date:
Subject: Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed