On Thursday 06 September 2001 20:49, Tom Lane wrote:
> Denis Perchine <[EMAIL PROTECTED]> writes:
> Okay. As a temporary recovery measure, I'd suggest reducing that
> particular elog from STOP to DEBUG level. That will let you start up
> and run the database. You'll need to look through your tables and try
> to figure out which one(s) have lost data. It might be interesting to
> try to figure out just which page has the bad LSN value --- that might
> give us a clue why the WAL did not provide protection against this
> failure. Unfortunately XLogFlush doesn't have any idea who its caller
> is, so the only way I can think of to check that directly is to set a
> breakpoint at this error report and look at the call stack.
OK. I will do this tomorrow. I have no space, and I forced to tgz, untgz
database.
--
Sincerely Yours,
Denis Perchine
----------------------------------
E-Mail: [EMAIL PROTECTED]
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
