> > Sep 6 02:09:30 mx postgres[13468]: [9] FATAL 2:
> > XLogFlush: request(1494286336, 786458) is not satisfied --
> > flushed to (23, 2432317444)
First note that Denis could just restart with wal_debug = 1
to see bad request, without code change. (We should ask ppl
to set wal_debug ON in the
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 you
Denis Perchine <[EMAIL PROTECTED]> writes:
> Sep 6 02:09:30 mx postgres[13468]: [9] FATAL 2: XLogFlush: request(1494286336,
>786458) is not satisfied --
> flushed to (23, 2432317444)
Yeek. Looks like you have a page somewhere in the database with a bogus
LSN value (xlog pointer) ... and, mo
Denis Perchine <[EMAIL PROTECTED]> writes:
> Sep 5 08:42:30 mx postgres[5341]: [9] FATAL 2: XLogFlush: request is not satisfied
Hmm. I think you must be running into some kind of logic bug (boundary
condition maybe?) in XLogFlush. Could you add some debugging printouts,
along the line of
**
Hello,
I have quite strange problem. Postgres refuses to start.
This is 7.1.2. Actually this is Aug 15 snapshot of REL7_1_STABLE branch.
This is what should be 7.1.2. Any ideas how to repair data?
This is quite urgent. The system is live, and now stopped.
Sep 5 08:42:30 mx postgres[5341]
