2009/10/23 João Eugenio Marynowski joa...@gmail.com
I thought this would solve my problems but not yet ...
the block that I found is not presenting error...
find_bad_block
(514708,16)
(1 registro)
blockId / blocks_per_chunk = 514708 / 131072 = 3,9269104
base/21058
2009/10/23 Robert Haas robertmh...@gmail.com
Well, that's not really the problem. Your data is corrupted -
increasing the index row size is not going to fix it.
I'm not really knowledgeable enough about the guts of the database to
know whether there are lower-level tools that could be used
2009/10/23 Dimitri Fontaine dfonta...@hi-media.com
João Eugenio Marynowski joa...@gmail.com writes:
2009-10-16 16:11:47 BRT 192.168.0.29 ERROR: invalid page header in
block 462821 of relation ...
It could be that the following will prove helpful:
http://archives.postgresql.org/pgsql
Hi everybody,
Can someone help me how to repair the problem below, I'm using Postgres
8.2.5:
- after appeared the erros below in selects, vacuum and dump in one table:
2009-10-16 16:07:06 BRT 192.168.0.87 ERROR: could not access status of
transaction 29024764
2009-10-16 16:07:06 BRT 192.168.0.87
Hi
Can someone help me how to repair the problem below, I'm using Postgres
8.2.5:
- after appeared the erros below in selects, vacuum and dump in one table:
2009-10-16 16:07:06 BRT 192.168.0.87 ERROR: could not access status of
transaction 29024764
2009-10-16 16:07:06 BRT 192.168.0.87 DETAIL:
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...
2009/10/22 Joshua D. Drake j...@commandprompt.com
On Thu, 2009-10-22 at 14:28 -0200, João Eugenio Marynowski wrote:
Hi
Repair
:
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 robertmh...@gmail.com
On Thu, Oct 22, 2009 at 10:34 PM, João Eugenio Marynowski
joa...@gmail.com wrote:
The hardware is ok because we
