Hello,
I see incorrect checksum detected on "global/pg_filenode.map" when "VACUUM
FULL" is executed.
The error message didn't repeat. It showed up only once.
Is this expected? Can someone give me a plausible scenario why this happened?
Aug 16 20:51:19 postgres[22329]: [2-1] FATAL: relation
John, Michael,
Thanks. The server is Dell PowerEdge R720.
The checksum error only was reported only once so I guess it was automatically
fixed immediately.
The log was output only one time while the box was running very long time (> 1
year.).
I have hundreds of the machines with same confi
, John R Pierce wrote:
> On 8/21/2016 9:13 PM, Tatsuki Kadomoto wrote:
>>
>> Can we point out a specific bug that can lead to this?
>
>
> 9.2.6 fixed several data corruption bugs,
> https://www.postgresql.org/docs/current/static/release-9-2-6.html
>
> 9.2.9 fixed
Michael,
Thank you very much.
Regards,
Tatsuki
From: Michael Paquier
Sent: Monday, August 22, 2016 5:02:40 PM
To: Tatsuki Kadomoto
Cc: John R Pierce; PostgreSQL mailing lists
Subject: Re: [GENERAL] incorrect checksum detected on "global/pg_filenod
From: Kevin Grittner
Sent: Tuesday, August 23, 2016 3:07:03 AM
To: Michael Paquier
Cc: Tatsuki Kadomoto; John R Pierce; PostgreSQL mailing lists
Subject: Re: [GENERAL] incorrect checksum detected on "global/pg_filenode.map"
when VACUUM FULL is executed
On Mon, Aug 22, 2016 at 3:02
Michael,
In my case, it only detected once.
Does Postgre have any mechanism to correct the mapping file automatically?
Regards,
Tatsuki
Sent from my ASUS
オリジナルのメッセージ
送信元:Michael Paquier
送信済み:Fri, 26 Aug 2016 09:05:53 +0900
送信先:Tatsuki Kadomoto
Cc:Kevin Grittner ,John R Pierce
