Re: could not read block... how could I identify/fix

From: Vick Khera <vivek(at)khera(dot)org>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: could not read block... how could I identify/fix
Date: 2012-03-29 14:08:50
Message-ID: CALd+dccZw7ghk_t32QkzpEa-XvAG=6nL4Mk0vX4+AHZjVM43Dg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Mar 28, 2012 at 6:31 PM, Naoko Reeves <naokoreeves(at)gmail(dot)com> wrote:
> Do you think this should be the next step I might take?
> Could you give me an advice of how I could identify corrupted error.

It seems to me that since you can successfully dump the table (I
assume you validated the data was all there somehow), you should go
ahead and dump your whole DB, delete the current one, create it again,
then restore it from scratch.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Arvind Singh 2012-03-29 14:09:20 More PG Log
Previous Message Maxim Boguk 2012-03-29 10:57:53 Why checkpoint_timeout had maximum value of 1h?