Miguel wrote:
Tom Lane wrote:
Increasing the WAL start address might help (see the pg_resetxlog man
page). Realize that you're probably going to be dealing with corrupted
data, however :-(
regards, tom lane
Ops, foget the last email, i reread the man, this is what i have to
Tom Lane wrote:
Increasing the WAL start address might help (see the pg_resetxlog man
page). Realize that you're probably going to be dealing with corrupted
data, however :-(
regards, tom lane
Yeah, i know, but i only want to be able to finish the dump, i must
exec
Miguel <[EMAIL PROTECTED]> writes:
> ERROR: xlog flush request 98/E3E83848 is not satisfied --- flushed only
> to 98/C364344
> what can i do?
Increasing the WAL start address might help (see the pg_resetxlog man
page). Realize that you're probably going to be dealing with corrupted
data, howev
Hi, i had a server crash and after that , postgres refused to start, i
read on the list that pg_resetxlog could help me, indeed, after i run
pg_resetxlog dir_data, postgres started again, but i look a lot of these
errors:
CONTEXT: writing block 1 of relation 1663/17231/69118230
WARNING: coul
