PITR Error Message assistance

Could I ask for feedback on the error messages used with the archiver
and restore functionality? Possibly those of you with a hand in the
Error Message style guide?

The messages need the eye of some administrators to suggest some better
phrases. Some probably need some explanation, but I'll leave that for
you to decide which...and what you think it should say instead. Thinking
that if they need explanation, they probably are worded wrongly...

These are copied straight from recent patch:

+ elog(WARNING, "could not set notify for archiver to read log file %u,
segment %u",


+   ereport(LOG,
+   (errmsg("recovery.conf found...starting archive recovery")));

+  elog(LOG, "redo: restored \"%s\" from archive", restoreXlog);

+                 elog(LOG, "rename failed %s %s",recoveryXlog, lastrecoXlog);

+  elog(LOG, "redo: cannot restore \"%s\" from archive", restoreXlog);


+  ereport(ERROR,
+                         (errcode_for_file_access(),
+                          errmsg("could not write archive_status file \"%s\"
",
+                               tmppath)));

+  elog(LOG, "redo: moving last restored xlog to %s", tmppath);

+  elog(LOG, "redo: rename failed");

+  elog(LOG, "redo: archive chain ends; using local copy of \"%s\"",
restoreXlog);


+   (errmsg("archive recovery complete")));


+   ereport(LOG,
! (errmsg("too many transaction log files, removing \"%s\"",
xlde->d_name)));

+                 ereport(WARNING,
+                 (errcode_for_file_access(),
+                  errmsg("chkpt: cannot find archive_status file: %s ",
+                         rlogpath)));


+                  elog(WARNING, "chkpt: archiving not yet started for log file
%s",
+                         xlog);



DEBUG MESSAGES

+         elog(LOG, "backend: written %s", rlogpath );
+

+   elog(LOG, "postmaster: WAKEN_ARCHIVER received, sending SIGUSR1 to
archiver");

+             elog(LOG, "chkpt: archiving done for log file %s",
+                            xlog);

+             elog(LOG, "redo: system(%s)", xlogRestoreCmd);


Thanks,

Best regards, Simon Riggs