Re: could not read block... how could I identify/fix - Mailing list pgsql-general

From Vick Khera
Subject Re: could not read block... how could I identify/fix
Date
Msg-id CALd+dccZw7ghk_t32QkzpEa-XvAG=6nL4Mk0vX4+AHZjVM43Dg@mail.gmail.com
Whole thread Raw
In response to could not read block... how could I identify/fix  (Naoko Reeves <naokoreeves@gmail.com>)
Responses Re: could not read block... how could I identify/fix  (Naoko Reeves <naokoreeves@gmail.com>)
List pgsql-general
On Wed, Mar 28, 2012 at 6:31 PM, Naoko Reeves <naokoreeves@gmail.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.

pgsql-general by date:

Previous
From: Maxim Boguk
Date:
Subject: Why checkpoint_timeout had maximum value of 1h?
Next
From: Arvind Singh
Date:
Subject: More PG Log