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 CAB7nPqSaXJDXPVmywAKHqatfQ5Wb4pVw=0y6ARs9VrqxCG=9fQ@mail.gmail.com
Whole thread Raw
In response to Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed  (John R Pierce <pierce@hogranch.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 Mon, Aug 22, 2016 at 1:31 PM, John R Pierce <pierce@hogranch.com> 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 a GiST index corruption problem...
> https://www.postgresql.org/docs/current/static/release-9-2-9.html
>
> I would upgrade to 9.2.18, the latest 9.2 version,
> https://www.postgresql.org/docs/current/static/release-9-2-18.html

Yep, this is mandatory. You are taking a lot of risks here by only using 9.2.4.
--
Michael

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed
Next
From: Thomas Güttler
Date:
Subject: Re: PG vs ElasticSearch for Logs