Re: after using pg_resetxlog, db lost

From: Richard Huxton <dev(at)archonet(dot)com>
To: wang_zc(at)yahoo(dot)co(dot)uk
Cc: pgsql-general(at)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us
Subject: Re: after using pg_resetxlog, db lost
Date: 2004-06-01 15:57:00
Message-ID: 40BCA74C.70407@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Josué Maldonado 2004-06-01 16:12:30 Re: Insert speed question
Previous Message zhicheng wang 2004-06-01 15:35:10 Re: after using pg_resetxlog, db lost