On Thu, Mar 29, 2012 at 7:47 PM, Naoko Reeves wrote:
> Vick,
> Thank you very much. Yes, I just go ahead did what you said and all appears
> to be fine.
You definitely need to check your hardware for faults, especially the
one that caused your server to crash. Run some memory tests, drive
tests
Vick,
Thank you very much. Yes, I just go ahead did what you said and all appears
to be fine.
On Thu, Mar 29, 2012 at 7:08 AM, Vick Khera wrote:
> On Wed, Mar 28, 2012 at 6:31 PM, Naoko Reeves
> wrote:
> > Do you think this should be the next step I might take?
> > Could you give me an advice
On Wed, Mar 28, 2012 at 6:31 PM, Naoko Reeves wrote:
> Version: "PostgreSQL 8.4.6 on
Oh, and also upgrade to 8.4.11 to ensure you do not have any known
data loss bugs.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgres
On Wed, Mar 28, 2012 at 6:31 PM, Naoko Reeves 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 someho
There was a hardware crash.
Since then INSERT to one table is failing with the following message:
ERROR: could not read block 11857 of relation base/16396/3720450: read
only 0 of 8192 bytes
ERROR: could not read block 11805 of relation base/16396/3720450: read
only 0 of 8192 bytes
Similar error
