Re: Postgres 8.3 archive_command

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Rudolf van der Leeden" <vanderleeden(at)logicunited(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Postgres 8.3 archive_command
Date: 2007-11-21 16:18:35
Message-ID: 474405FB.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> On Wed, Nov 21, 2007 at 8:49 AM, in message
<1195656591(dot)4246(dot)42(dot)camel(at)ebony(dot)site>, Simon Riggs <simon(at)2ndquadrant(dot)com>
wrote:

> Perhaps we should move the successful archived message to DEBUG1 now,
> except for the first message after the archiver starts or when the
> archive_command changes, plus one message every 255 segments? That would
> reduce the log volume in the normal case without endangering our ability
> to see what is happening.

I would prefer to always log the archives; it has proven useful in
investigating what's going on when our backup stream "stalls". How
much other stuff would I be getting if I had to turn on DEBUG1 to
see this? Would it be overkill to add a GUC to configure the log
level of archiving?

For less active databases, where we rarely get more than one
segment per hour, it would be kinda odd to see an archive logged
once every couple weeks.

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-11-21 16:27:14 Re: Postgres 8.3 archive_command
Previous Message Alvaro Herrera 2007-11-21 16:17:05 Re: wrong behavior using to_char() again