pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter_e@gmx.net>
To: Simon Riggs <simon@2ndquadrant.com>
To: pgsql-admin@postgresql.org
Subject: Re: PITR Error Message assistance
Date: Wed, 30 Jun 2004 08:49:18 +0200
Message-ID: <200406300849.18058.peter_e@gmx.net> (raw)
In-Reply-To: <1088541547.3266.7534.camel@stromboli>
References: <auto-000005536314@davinci.ethosmedia.com>
	<200406291036.48477.josh@agliodbs.com>
	<1088541547.3266.7534.camel@stromboli>

Simon Riggs wrote:
> + elog(WARNING, "could not set notify for archiver to read log file
> %u, segment %u",

Reason? (disk full, network down, leap year?)

I think elog() calls don't get translated.  You should always use 
ereport.  Tom would know more about the distinction.

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

comma

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

Reason?

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

Reason?

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

Probably a user doesn't know what "xlog" is.  Also, I don't like the 
prefix: style you use.  Just tell what happened.

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

We don't write "foo failed", but "could not do foo".  And again: reason?

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

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

How/where is the limit defined?

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

There is enough space that you can write "checkpoint".  Or actually 
don't write anything.  What is the archive_status file?

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

What does that tell me?


> DEBUG MESSAGES

Debug messages should have a DEBUG severity.

>
> + 		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);




view thread (5+ messages)  latest in thread

Message-ID: <200406300849.18058.peter_e@gmx.net>
Permalink:  ../200406300849.18058.peter_e@gmx.net/
Also on:    postgresql.org/message-id/200406300849.18058.peter_e@gmx.net

 · 

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: peter_e@gmx.net, simon@2ndquadrant.com
  Subject: Re: PITR Error Message assistance
  In-Reply-To: <200406300849.18058.peter_e@gmx.net>
  References: <auto-000005536314@davinci.ethosmedia.com> <200406291036.48477.josh@agliodbs.com> <1088541547.3266.7534.camel@stromboli> <200406300849.18058.peter_e@gmx.net>

* 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