Re: table corrupted
От | João Eugenio Marynowski |
---|---|
Тема | Re: table corrupted |
Дата | |
Msg-id | 840f304c0910231226t889e818p662d6d284fc07143@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: table corrupted (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
<div class="gmail_quote">2009/10/23 Robert Haas <span dir="ltr"><<a href="mailto:robertmhaas@gmail.com">robertmhaas@gmail.com</a>></span><br/><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"></div>Well,that's not really the problem. Your data is corrupted -<br /> increasing the index row size is notgoing to fix it.<br /><br /> I'm not really knowledgeable enough about the guts of the database to<br /> know whetherthere are lower-level tools that could be used to rescue<br /> your data. I wonder if you'd have any luck selectingdata a few rows<br /> at a time (LIMIT 100, say, without ORDER BY). That might at least<br /> enable you to getsome of the data out of there, if there are some<br /> pages that are undamaged. But I'm grasping at straws here.<br/><font color="#888888"><br /> ...Robert<br /></font></blockquote></div>I ask about the index row size because Ican't re-index the database and I've a server for tests and in this I removed the pk and can't recreate the index becauseit showing error about size row limit indices.<br />And, only occurs erros when you run a query involving the recordsdamaged. I'm trying to identify them (less of 1% of the total registers).<br /><br /><br />
В списке pgsql-hackers по дате отправления: