Skip site navigation (1) Skip section navigation (2)

Re: Problems starting up postgres

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Denis Perchine <dyp(at)perchine(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Problems starting up postgres
Date: 2001-09-05 16:23:59
Message-ID: 14017.999707039@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Denis Perchine <dyp(at)perchine(dot)com> 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

*** src/backend/access/transam/xlog.c~	Wed Sep  5 12:18:07 2001
--- src/backend/access/transam/xlog.c	Wed Sep  5 12:20:17 2001
***************
*** 1266,1272 ****
  			XLogWrite(WriteRqst);
  			S_UNLOCK(&(XLogCtl->logwrt_lck));
  			if (XLByteLT(LogwrtResult.Flush, record))
! 				elog(STOP, "XLogFlush: request is not satisfied");
  			break;
  		}
  		S_LOCK_SLEEP(&(XLogCtl->logwrt_lck), spins++, XLOG_LOCK_TIMEOUT);
--- 1266,1274 ----
  			XLogWrite(WriteRqst);
  			S_UNLOCK(&(XLogCtl->logwrt_lck));
  			if (XLByteLT(LogwrtResult.Flush, record))
! 				elog(STOP, "XLogFlush: request (%u, %u) is not satisfied --- flushed to (%u, %u)",
! 					 record.xlogid, record.xrecoff,
! 					 LogwrtResult.Flush.xlogid, LogwrtResult.Flush.xrecoff);
  			break;
  		}
  		S_LOCK_SLEEP(&(XLogCtl->logwrt_lck), spins++, XLOG_LOCK_TIMEOUT);


(this patch is for current sources, line numbers are probably different
in 7.1.*)

BTW, how did you get into this state --- did you have a system crash?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-09-05 16:52:37
Subject: Re: libpgtcl doesn't use UTF encoding of TCL
Previous:From: Denis PerchineDate: 2001-09-05 15:47:40
Subject: Problems starting up postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group