I test this patch, it seems to fix this problem. I think recovery and WAL write
control are very difficult... So I make debug log which is more helpful for like
this trouble.
Sorry, attached my patch had very easy problem... Please used this patch.

Best regards,
--
NTT Open Sorce Software Center
Mitsumasa KONDO
diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
index 26c9ef3..2f8bf66 100644
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -2936,7 +2936,10 @@ XLogFileReadAnyTLI(uint32 log, uint32 seg, int emode, int sources)
		{
			fd = XLogFileRead(log, seg, emode, tli, XLOG_FROM_PG_XLOG, true);
			if (fd != -1)
+			{
+				elog(DEBUG1, "got WAL segment from pg_xlog");
				return fd;
+			}
		}
	}
-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

Reply via email to