I searched the various threads on the xlog -> wal rename and I couldn't
find any specific mention of why this was not renamed.
I have attached a patch in case it was an oversight rather than left
as-is on purpose.
Thanks,
--
-David
da...@pgmasters.net
diff --git a/src/backend/access/transam/xlog.c
b/src/backend/access/transam/xlog.c
index df4843f409..fd7bfa11d1 100644
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -3562,7 +3562,7 @@ XLogFileRead(XLogSegNo segno, int emode, TimeLineID tli,
set_ps_display(activitymsg, false);
restoredFromArchive = RestoreArchivedFile(path,
xlogfname,
-
"RECOVERYXLOG",
+
"RECOVERYWAL",
XLogSegSize,
InRedo);
if (!restoredFromArchive)
@@ -5550,10 +5550,10 @@ exitArchiveRecovery(TimeLineID endTLI, XLogRecPtr
endOfLog)
XLogArchiveCleanup(xlogfname);
/*
- * Since there might be a partial WAL segment named RECOVERYXLOG, get
rid
+ * Since there might be a partial WAL segment named RECOVERYWAL, get rid
* of it.
*/
- snprintf(recoveryPath, MAXPGPATH, XLOGDIR "/RECOVERYXLOG");
+ snprintf(recoveryPath, MAXPGPATH, XLOGDIR "/RECOVERYWAL");
unlink(recoveryPath); /* ignore any error */
/* Get rid of any remaining recovered timeline-history file, too */
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
