>>>"Jonah H. Harris" wrote:
> Joshua D. Drake wrote:
>
>> This reply is wholly inappropriate for a Pg list. We are here to
>> help people. If you have a consultancy, please feel free to list
>> that but any discussion of rates is just plain rude. Please use
>> better discretion in the future.
>>
On Mon, Oct 26, 2009 at 12:55 PM, Joshua D. Drake wrote:
> This reply is wholly inappropriate for a Pg list. We are here to help
> people. If you have a consultancy, please feel free to list that but any
> discussion of rates is just plain rude. Please use better discretion in
> the future.
>
Per
On Mon, 2009-10-26 at 09:14 -0400, Jonah H. Harris wrote:
> On Thu, Oct 22, 2009 at 7:16 PM, Joshua D. Drake
> wrote:
> On Thu, 2009-10-22 at 14:28 -0200, João Eugenio Marynowski
> wrote:
> > Hi
> >
> Repair? Not likely. Get past? Maybe.
>
> I don't know ho
On Thu, Oct 22, 2009 at 7:16 PM, Joshua D. Drake wrote:
> On Thu, 2009-10-22 at 14:28 -0200, João Eugenio Marynowski wrote:
> > Hi
> >
> Repair? Not likely. Get past? Maybe.
>
I don't know how valuable your data is, but I've performed data recovery on
tens of PG databases suffering from both hard
2009/10/23 João Eugenio Marynowski
> 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/21271.3
> chun
2009/10/23 Dimitri Fontaine
> João Eugenio Marynowski 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-general/2007-07/msg00506.php
>
2009/10/23 Robert Haas
> 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 to rescue
> your
João Eugenio Marynowski 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-general/2007-07/msg00506.php
http://pgsql.tapoueh.org/site/html/news/2
On Thu, Oct 22, 2009 at 11:00 PM, João Eugenio Marynowski
wrote:
> 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
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:
ERR
On Thu, Oct 22, 2009 at 10:34 PM, João Eugenio Marynowski
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
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
> On Thu, 2009-10-22 at 14:28 -0200, João Eugenio Marynowski wrote:
> > Hi
> >
> Repair? Not likely. Get past
On Thu, 2009-10-22 at 14:28 -0200, João Eugenio Marynowski wrote:
> Hi
>
Repair? Not likely. Get past? Maybe.
set zero_damaged_pages to on;
vacuum verbose;
I would do a hardware check too.
Joshua D. Drake
> Can someone help me how to repair the problem below, I'm using
> Postgres 8.2.5:
> - a
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: Co
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 D
15 matches
Mail list logo
