Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tatsuki Kadomoto <tatsuki(dot)kadomoto(at)proceranetworks(dot)com>
Cc: Kevin Grittner <kgrittn(at)gmail(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed
Date: 2016-08-26 00:05:50
Message-ID: CAB7nPqRSFx974uQPnqUSDcBh75nQ7bwrsbmf-MBXnCs3nFr_tQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Aug 25, 2016 at 9:48 PM, Tatsuki Kadomoto
<tatsuki(dot)kadomoto(at)proceranetworks(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tatsuki Kadomoto 2016-08-26 00:09:43 Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed
Previous Message John R Pierce 2016-08-25 23:51:27 Re: LOG: could not fork new process for connection: Cannot allocate memory