Skip site navigation (1) Skip section navigation (2)

[Fwd: Re: [HACKERS] Postgres 8.3 archive_command]

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: pgsql-patches(at)postgresql(dot)org
Subject: [Fwd: Re: [HACKERS] Postgres 8.3 archive_command]
Date: 2007-11-22 09:32:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Small patch to reduce archive messages to DEBUG1 attached.

-------- Forwarded Message --------
From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Rudolf van der Leeden
<vanderleeden(at)logicunited(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Postgres 8.3 archive_command
Date: Wed, 21 Nov 2007 18:27:46 +0000

On Wed, 2007-11-21 at 12:24 -0500, Tom Lane wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> > Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote: 
> >> Just to clarify: I don't object to lowering "successfully archived"
> >> messages to DEBUG1, if the field consensus is that it's too chatty.
> >> What I didn't like was the idea of logging some events but not other
> >> identical events.
> > Agreed on the intermittent logging.  I don't feel it's too chatty,
> > but on the other hand, I could always change the logging level on
> > the fly if I was investigating a problem, so it wouldn't be much of
> > an inconvenience to switch it if it bugs others.
> Also, you can always tweak your archive_command script to do some
> logging of its own, so it's always possible to make the thing more
> noisy if you need to.  Less noisy, though, is hard without changing
> the server code.

OK, both of those thoughts are good, so happy now with DEBUG1 for
success messages: "archived transaction log file..."

Enclosed patch to set archived message to DEBUG1.

I've got a few other comments for PITR docs, so I'll mention this also
in forthcoming patch.

  Simon Riggs

Attachment: archive_success_debug1.v1.patch
Description: text/x-patch (663 bytes)

pgsql-patches by date

Next:From: Marko KreenDate: 2007-11-22 12:16:26
Subject: plpython crash on exception
Previous:From: Bruce MomjianDate: 2007-11-21 23:13:02
Subject: Re: [BUGS] BUG #3770: Follow up: Fail to make bcc32.mak for libpq

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group