| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Simplifying replication |
| Date: | 2010-10-28 05:13:26 |
| Message-ID: | 4CC90676.4080503@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gnanakumar | 2010-10-28 07:57:02 | Re: pg_ctl: server does not shut down |
| Previous Message | Andrew Dunstan | 2010-10-28 04:08:39 | Re: Composite Types and Function Parameters |