X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D7316D1B29D for ; Wed, 30 Jun 2004 03:49:23 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 71865-04 for ; Wed, 30 Jun 2004 06:49:22 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by svr1.postgresql.org (Postfix) with SMTP id 6474FD1B23E for ; Wed, 30 Jun 2004 03:49:18 -0300 (ADT) Received: (qmail 4663 invoked by uid 65534); 30 Jun 2004 06:49:18 -0000 Received: from dsl-213-023-250-211.arcor-ip.net (EHLO colt.pezone.net) (213.23.250.211) by mail.gmx.net (mp016) with SMTP; 30 Jun 2004 08:49:18 +0200 X-Authenticated: #495269 From: Peter Eisentraut To: Simon Riggs , pgsql-admin@postgresql.org Subject: Re: PITR Error Message assistance Date: Wed, 30 Jun 2004 08:49:18 +0200 User-Agent: KMail/1.5.1 References: <200406291036.48477.josh@agliodbs.com> <1088541547.3266.7534.camel@stromboli> In-Reply-To: <1088541547.3266.7534.camel@stromboli> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200406300849.18058.peter_e@gmx.net> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/393 X-Sequence-Number: 14053 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);