Re: archive wal's failure and load increase. - Mailing list pgsql-performance

From Simon Riggs
Subject Re: archive wal's failure and load increase.
Date
Msg-id 1159541620.2649.10.camel@holly
Whole thread Raw
In response to Re: archive wal's failure and load increase.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: archive wal's failure and load increase.
List pgsql-performance
On Fri, 2006-09-29 at 10:29 -0400, Tom Lane wrote:
> 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.

Yes, but not enough.

PreallocXlogFiles() adds only a *single* xlog file, sometimes.

On a busy system, that would be used up too quickly to make a
difference. After that the effect of adding new files would continue as
suggested.

If it did add more than one... it might work better for this case.

> 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.

Still the best explanation for me.

--
  Simon Riggs
  EnterpriseDB   http://www.enterprisedb.com


pgsql-performance by date:

Previous
From: "Merlin Moncure"
Date:
Subject: Re: Performace Optimization for Dummies
Next
From: "Jim C. Nasby"
Date:
Subject: Re: any hope for my big query?