Re: Index corruption & broken clog

From: Benoit Lobréau <benoit(dot)lobreau(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Index corruption & broken clog
Date: 2017-10-13 08:25:42
Message-ID: CAPE8EZ4OQVT0VbAY2H6s2Koq6HYTroZM-EG=6RMGGrpndF2phg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks for the help.

> Shut down the corrupted database and make a physical backup of it.
>

I did it before trying anything.

> Check the disks and memory on the machine where the problem occurred.
>

We are using virtual machines (VMWare). I will ask then to investigate
anyway.

> You can try to salvage data from the corrupted tables, either
> using "zero_damaged_pages" (but that will only work if the page
> header is corrupted), or by excluding problematic tuples by their
> "ctid".
>

Thanks will try.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Benoit Lobréau 2017-10-13 08:55:38 Re: Index corruption & broken clog
Previous Message KES 2017-10-13 08:13:43 Re: Fwd: [BUGS] BUG #14850: Implement optinal additinal parameter for 'justify' date/time function