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

From Tom Lane
Subject Re: archive wal's failure and load increase.
Date
Msg-id 15270.1159540162@sss.pgh.pa.us
Whole thread Raw
In response to Re: archive wal's failure and load increase.  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: archive wal's failure and load increase.  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: Bill Moran
Date:
Subject: Re: Performace Optimization for Dummies
Next
From: "Merlin Moncure"
Date:
Subject: Re: Performace Optimization for Dummies