Re: Postgres 8.3 archive_command - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Postgres 8.3 archive_command
Date
Msg-id 1195666241.4246.57.camel@ebony.site
Whole thread Raw
In response to Re: Postgres 8.3 archive_command  ("Zeugswetter Andreas ADI SD" <Andreas.Zeugswetter@s-itsolutions.at>)
Responses Re: Postgres 8.3 archive_command
Re: Postgres 8.3 archive_command
List pgsql-hackers
On Wed, 2007-11-21 at 18:16 +0100, Zeugswetter Andreas ADI SD 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.
> 
> Wouldn't it be more useful to increase the WAL segment size on such
> installations
> that switch WAL files so frequently that it is a problem for the log ?
> 
> This currently needs a recompile. I wondered for some time now whether
> 16 Mb isn't
> too low for current hw. Maybe it is time for making WAL segment size
> changeable 
> in the conf with a clean shutdown.

I think its too late in the release cycle to fully consider all the
implications of that. 16MB is hardcoded in lots of places. The
performance advantages of that have been mostly removed in 8.3, you
should note.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgres 8.3 archive_command
Next
From: Hannes Eder
Date:
Subject: Re: random dataset generator for SKYLINE operator