Re: Postgres 8.3 archive_command - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Postgres 8.3 archive_command
Date
Msg-id 1195663366.4246.47.camel@ebony.site
Whole thread Raw
In response to Re: Postgres 8.3 archive_command  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Postgres 8.3 archive_command  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, 2007-11-21 at 11:27 -0500, Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
> > 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.
> 
> That would confuse people terribly, and it *would* endanger our ability
> to see what was happening, 254 times out of 255.

That's my feeling too, just wanted to check it still made sense for
y'all.

--  Simon Riggs 2ndQuadrant  http://www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: plperl failure on OS X 10.5(.1)
Next
From: Tom Lane
Date:
Subject: Re: Postgres 8.3 archive_command