From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Allow time delayed standbys and recovery |
Date: | 2013-12-19 19:19:21 |
Message-ID: | CAA-aLv7ieqbd6wxQg=-q8hc1Rc7-K65KkrNMvYwzpHg+X=-NTQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 12 December 2013 10:56, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Allow time delayed standbys and recovery
>
> Set min_recovery_apply_delay to force a delay in recovery apply for commit and
> restore point WAL records. Other records are replayed immediately. Delay is
> measured between WAL record time and local standby time.
>
> Robert Haas, Fabrízio de Royes Mello and Simon Riggs
> Detailed review by Mitsumasa Kondo
Could a note be added about the additional disk space requirements for
WAL on the standby? If one is delaying replay, WAL files created over
the delayed period will build up in pg_xlog on the standby until
they're consumed upon replay, so considerations about storing those
additional files will need to be made. It may otherwise trip up
anyone who, say, delays replay by 24 hours in a busy production
environment, and finds they have run out of disk space and no longer
have a valid standby.
--
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2013-12-19 19:33:28 | Re: pgsql: Allow time delayed standbys and recovery |
Previous Message | Fujii Masao | 2013-12-19 17:34:04 | pgsql: Add tab completion for ALTER SYSTEM SET in psql. |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2013-12-19 19:26:38 | Re: pg_rewarm status |
Previous Message | Cédric Villemain | 2013-12-19 19:04:43 | Re: pg_rewarm status |