From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: cedric@dreamgnu.com
Cc: pgsql-performance@postgresql.org
Subject: Re: archive wal's failure and load increase.
Date: Fri, 29 Sep 2006 10:29:22 -0400
Message-ID: <15270.1159540162@sss.pgh.pa.us> (raw)
In-Reply-To: <1159527513.2767.296.camel@holly>
References: <451C2572.20800@dreamgnu.com>
<1159527513.2767.296.camel@holly>
Simon Riggs <simon@2ndquadrant.com> writes:
> We discussed putting PreallocXlogFiles() in bgwriter once before, but I
> think last time we discussed that idea it was rejected, IIRC.
We already do that: it's called a checkpoint. If the rate of WAL
generation was more than checkpoint_segments per checkpoint_timeout,
then indeed there would be a problem with foreground processes having to
manufacture WAL segment files for themselves, but it would be a bursty
thing (ie, problem goes away after a checkpoint, then comes back).
It's a good thought but I don't think the theory holds water for
explaining Cedric's problem, unless there was *also* some effect
preventing checkpoints from completing ... which would be a much more
serious problem than the archiver failing.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, simon@2ndquadrant.com, cedric@dreamgnu.com
Subject: Re: archive wal's failure and load increase.
In-Reply-To: <15270.1159540162@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox