Re: Postgres 8.3 archive_command

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Rudolf van der Leeden <vanderleeden(at)logicunited(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Postgres 8.3 archive_command
Date: 2007-11-21 16:42:46
Message-ID: 1195663366.4246.47.camel@ebony.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2007-11-21 at 11:27 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-11-21 16:57:32 Re: Postgres 8.3 archive_command
Previous Message Tom Lane 2007-11-21 16:39:14 Re: plperl failure on OS X 10.5(.1)