> I sort of agree with you that the current checkpoint_segments
> parameter is a bit hard to tune, at least if your goal is to control
> the amount of disk space that will be used by WAL files. But I'm not
> sure your proposal is better. Instead of having a complicated formula
> for predicting how much disk space would get used by a given value for
> checkpoint_segments, we'd have a complicated formula for the amount of
> WAL that would force a checkpoint based on max_wal_size.
Yes, but the complicated formula would then be *in our code* instead of
being inflicted on the user, as it now is.
-- -- Josh Berkus PostgreSQL Experts Inc.
http://www.pgexperts.com