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: John R Pierce <pierce(at)hogranch(dot)com>
Cc: 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-22 04:34:30
Message-ID: CAB7nPqSaXJDXPVmywAKHqatfQ5Wb4pVw=0y6ARs9VrqxCG=9fQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Aug 22, 2016 at 1:31 PM, John R Pierce <pierce(at)hogranch(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Павел Филонов 2016-08-22 06:53:00 Why insertion throughput can be reduced with an increase of batch size?
Previous Message John R Pierce 2016-08-22 04:31:52 Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed