Re: Postgres 8.3 archive_command

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Zeugswetter Andreas ADI SD <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at>
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 17:30:41
Message-ID: 1195666241.4246.57.camel@ebony.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannes Eder 2007-11-21 17:31:00 Re: random dataset generator for SKYLINE operator
Previous Message Tom Lane 2007-11-21 17:24:40 Re: Postgres 8.3 archive_command