pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Josh Berkus <josh@agliodbs.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Simon Riggs <simon@2ndQuadrant.com>
Cc: Greg Stark <gsstark@mit.edu>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Simplifying replication
Date: Wed, 27 Oct 2010 22:13:26 -0700
Message-ID: <4CC90676.4080503@agliodbs.com> (raw)
In-Reply-To: <AANLkTin4ABkcfJTfY9=0o6h_Woz_NAeTfMxSJGzkbhc7@mail.gmail.com>
References: <201010220022.o9M0M8Q29438@momjian.us>
	<4CC0DEDE.7060707@agliodbs.com>
	<AANLkTin0RfGOvk20vLYYfCDzdf5Sf94aQ5V-xOBB+Kqx@mail.gmail.com>
	<AANLkTik-L-68UpwgyBh5HtROzkEYQ297fiy7C-c6qRfX@mail.gmail.com>
	<1288096049.1587.253.camel@ebony>
	<4CC8931D.3040800@agliodbs.com>
	<AANLkTin4ABkcfJTfY9=0o6h_Woz_NAeTfMxSJGzkbhc7@mail.gmail.com>


> 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

view thread (50+ messages)  latest in thread

Message-ID: <4CC90676.4080503@agliodbs.com>
Permalink:  ../4CC90676.4080503@agliodbs.com/
Also on:    postgresql.org/message-id/4CC90676.4080503@agliodbs.com

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: josh@agliodbs.com, robertmhaas@gmail.com, simon@2ndQuadrant.com, gsstark@mit.edu, bruce@momjian.us
  Subject: Re: Simplifying replication
  In-Reply-To: <4CC90676.4080503@agliodbs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox