Checksum error and VACUUM FULL

From: Tatsuki Kadomoto <tatsuki(dot)kadomoto(at)proceranetworks(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Checksum error and VACUUM FULL
Date: 2016-08-25 09:45:30
Message-ID: BN6PR08MB26585EF0A281ACCBEB7B75DB93ED0@BN6PR08MB2658.namprd08.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, gurus,

I faced incorrect checksum on "global/pg_filenode.map" at the right timing "VACUUM FULL" is executed and session was aborted.

Aug 16 20:51:19 postgres[22329]: [2-1] FATAL: relation mapping file "global/pg_filenode.map" contains incorrect checksum

Aug 16 20:51:19 postgres[22329]: [2-2] STATEMENT: SELECT id,readbm,writebm,survbm,timeout FROM Users WHERE username='packetlogicd' AND password=md5('xxxxx')

I'm reading the comment in src/backend/utils/cache/relmapper.c .

===
Therefore mapped catalogs can only be relocated by operations such as VACUUM FULL and CLUSTER, which make no transactionally-significant changes: it must be safe for the new file to replace the old, even if the transaction itself aborts.
===

Does this comment mean it's expected to get this kind of checksum error if the timing is really bad?

Regards,
Tatsuki

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Artur Zakirov 2016-08-25 10:11:00 Re: Bug in to_timestamp().
Previous Message amul sul 2016-08-25 09:10:29 Re: Bug in to_timestamp().