Re: after using pg_resetxlog, db lost - Mailing list pgsql-general

From Richard Huxton
Subject Re: after using pg_resetxlog, db lost
Date
Msg-id 40BCA74C.70407@archonet.com
Whole thread Raw
In response to Re: after using pg_resetxlog, db lost  (zhicheng wang <wang_zc@yahoo.co.uk>)
Responses Re: after using pg_resetxlog, db lost  (zhicheng wang <wang_zc@yahoo.co.uk>)
Re: after using pg_resetxlog, db lost  (zhicheng wang <wang_zc@yahoo.co.uk>)
List pgsql-general
zhicheng wang wrote:
> Hi Richard Huxton
>
> sorry to have bothered you with trivial things.
>
> the reindex give these error:
>
> backend> REINDEX DATABASE miamevice;
> ERROR:  XLogFlush: request 0/BB4C3560 is not satisfied
> --- flushed only to 0/20001D8
> WARNING:  write error may be permanent: cannot write
> block 29 for 4205811/1249
> backend> \q;
> ERROR:  parser: parse error at or near "\" at
> character 1
> backend> q\;
> ERROR:  parser: parse error at or near "q" at
> character 1
> backend> LOG:  shutting down
> PANIC:  XLogFlush: request 0/BB4C3560 is not satisfied
> --- flushed only to 0/20001D8
> Aborted
>
>
> does this mean that we cannot recover our data?

Well the problems with "\q" are because you need to press CTRL+D to end
the session. The inability to write is something I've not seen before,
so I've cc'd Tom Lane on this.

It doesn't look good though.

--
   Richard Huxton
   Archonet Ltd

pgsql-general by date:

Previous
From: zhicheng wang
Date:
Subject: Re: after using pg_resetxlog, db lost
Next
From: Josué Maldonado
Date:
Subject: Re: Insert speed question