Re: table corrupted - Mailing list pgsql-hackers

From João Eugenio Marynowski
Subject Re: table corrupted
Date
Msg-id 840f304c0910222000y1451ce13rb34275edda020e30@mail.gmail.com
Whole thread Raw
In response to Re: table corrupted  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: table corrupted
List pgsql-hackers
I don't be able to select the data from table with pg_dump or select, both occur error...
how i can identified the register of a table independent the contends of the register, only control of the postgres?
I eliminate the index pk but now I don't be able to create begin because show the error:
ERROR:  index row requires 21776744 bytes, maximum size is 8191
How increase the index row?

--
João Eugenio Marynowski
(41) 9624-3933


2009/10/23 Robert Haas <robertmhaas@gmail.com>
On Thu, Oct 22, 2009 at 10:34 PM, João Eugenio Marynowski
<joaoem@gmail.com> wrote:
> The hardware is ok because we have migrated to other machine and the errors
> is the same
> zero_damaged_pages is on and the vaccum verbose don't show any error...

You need to dump (or otherwise extract) your data and load it into a
new cluster.  The one you have sounds like it's in bad shape.

...Robert

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: table corrupted
Next
From: Itagaki Takahiro
Date:
Subject: (WIP) VACUUM REWRITE - CLUSTER by ctid