On 10/17/15 10:25 AM, Michael Paquier wrote:
> I think that we should just suggest a reverse formula of the maximum
> soft limit of checkpoint_segments for max_wal_size in the release notes
> of 9.5, basically:
> (3 * your_old_checkpoint_segments + 1) * 16MB = max_wal_size
How about this patch?
On Wed, Oct 21, 2015 at 3:11 AM, Peter Eisentraut wrote:
> On 10/17/15 10:25 AM, Michael Paquier wrote:
> > I think that we should just suggest a reverse formula of the maximum
> > soft limit of checkpoint_segments for max_wal_size in the release notes
> > of 9.5, basically:
> >
On Sat, Oct 17, 2015 at 4:45 AM, Robert Haas wrote:
> On Fri, Oct 16, 2015 at 2:52 PM, Peter Eisentraut wrote:
> > The release notes say that checkpoint_segments has been replaced by
> > max_wal_size and min_wal_size, but there is no indication on how to
The release notes say that checkpoint_segments has been replaced by
max_wal_size and min_wal_size, but there is no indication on how to
convert between the old and new settings. I think a lot of people will
have checkpoint_segments delicately tuned, so we should at least give
them a hint on how
On Fri, Oct 16, 2015 at 2:52 PM, Peter Eisentraut wrote:
> The release notes say that checkpoint_segments has been replaced by
> max_wal_size and min_wal_size, but there is no indication on how to
> convert between the old and new settings. I think a lot of people will
> have