pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: pgsql-admin@postgresql.org
Subject: PITR Error Message assistance
Date: Tue, 29 Jun 2004 21:39:07 +0100
Message-ID: <1088541547.3266.7534.camel@stromboli> (raw)
In-Reply-To: <200406291036.48477.josh@agliodbs.com>
References: <auto-000005536314@davinci.ethosmedia.com>
	<200406291036.48477.josh@agliodbs.com>

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




view thread (5+ messages)  latest in thread

Message-ID: <1088541547.3266.7534.camel@stromboli>
Permalink:  ../1088541547.3266.7534.camel@stromboli/
Also on:    postgresql.org/message-id/1088541547.3266.7534.camel@stromboli

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: simon@2ndquadrant.com
  Subject: Re: PITR Error Message assistance
  In-Reply-To: <1088541547.3266.7534.camel@stromboli>
  References: <auto-000005536314@davinci.ethosmedia.com> <200406291036.48477.josh@agliodbs.com> <1088541547.3266.7534.camel@stromboli>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox