On Wed, 26 Feb 2014 at 13:55, Thom Brown <thom@linux.com> wrote:
>
> On 26 February 2014 13:32, Simon Riggs <simon@2ndquadrant.com> wrote:
>>
>> On 26 February 2014 13:07, Thom Brown <thom@linux.com> wrote:
>> > On 19 December 2013 19:33, Simon Riggs <simon@2ndquadrant.com> wrote:
>> >>
>> >> On 19 December 2013 19:19, Thom Brown <thom@linux.com> wrote:
>> >> > On 12 December 2013 10:56, Simon Riggs <simon@2ndquadrant.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.
>> >>
>> >> Thanks Thom, good point. I will add a note to the docs.
>> >
>> >
>> > Just a reminder that this note hasn't been added to the docs yet.
>>
>> Please cut a doc patch and I'll apply.
>
>
> Attached.
I know it's been 8 years, but I still think it would be a useful note
to add to the docs.
--
Thom
