From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
To: Josh Berkus <josh@agliodbs.com>
Cc: Simon Riggs <simon@2ndQuadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Greg Stark <gsstark@mit.edu>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Simplifying replication
Date: Sun, 31 Oct 2010 22:12:12 +0100
Message-ID: <m2lj5e83tf.fsf@2ndQuadrant.fr> (raw)
In-Reply-To: <4CC8931D.3040800@agliodbs.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>
Josh Berkus <josh@agliodbs.com> writes:
>> You have to put the WAL files *somewhere* while you do the base backup.
>
> Agreed. That's why I like the idea of having a
> max_wal_size/min_wal_time instead of keep_wal_segments or
> checkpoint_segments. It's relatively simple for a DBA to know how much
> disk space s/he has for WAL, total, before locking up the system.
What if that somewhere is as easy to setup as a PostgreSQL archive
cluster: set a GUC a two, start the server, then in the production
server have archive_mode = on and use some internal archive and restore
commands, like 'pg_archivewal -h host -p port …'?
It's only pushing the problem away, but in my mind the only reason why
we're still talking about the problem is *not* the wal related settings
but the current complexity of setting up a trustworthy archive server,
and the number of external tools required in the operation (shell, scp,
rsync, rm, etc…).
Or is it just me?
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
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: dimitri@2ndQuadrant.fr, josh@agliodbs.com, simon@2ndQuadrant.com, robertmhaas@gmail.com, gsstark@mit.edu, bruce@momjian.us
Subject: Re: Simplifying replication
In-Reply-To: <m2lj5e83tf.fsf@2ndQuadrant.fr>
* 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