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:28:29
Message-ID: CAB7nPqRT56Pr9d-z3d_gSUX5+HF6qZHxuW1TbKnLyQtSM_2r2A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Aug 26, 2016 at 9:09 AM, Tatsuki Kadomoto
<tatsuki(dot)kadomoto(at)proceranetworks(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2016-08-26 00:29:39 Re: LOG: could not fork new process for connection: Cannot allocate memory
Previous Message Tom Lane 2016-08-26 00:27:20 Re: Understanding Postgres Memory Usage