Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed

[Tatsuki Kadomoto <tatsuki.kadomoto@xxxxxxxxxxxxxxxxxxx>]

John, Michael,

Thanks for suggestion for upgrade. I know that's the way to go, but it's not so easy due to circumstances on my side.

Meanwhile, could you tell me what is this "global/pg_filenode.map" for?

Regards,

Tatsuki

---

From: pgsql-general-owner@xxxxxxxxxxxxxx <pgsql-general-owner@xxxxxxxxxxxxxx> on behalf of Michael Paquier <michael.paquier@xxxxxxxxx>
Sent: Monday, August 22, 2016 1:34:30 PM
To: John R Pierce
Cc: PostgreSQL mailing lists
Subject: Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed

 

On Mon, Aug 22, 2016 at 1:31 PM, John R Pierce <pierce@xxxxxxxxxxxx> 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


--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general