Re: recovery_min_apply-delay and remote_apply - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: recovery_min_apply-delay and remote_apply
Date
Msg-id CAEepm=29BEQiWCw7aPTX_TSneuVN3f3gg0cniW5w7C9C=7jjxg@mail.gmail.com
Whole thread Raw
In response to recovery_min_apply-delay and remote_apply  (Bernd Helmle <mailings@oopsware.de>)
Responses Re: recovery_min_apply-delay and remote_apply
List pgsql-hackers
On Sat, Sep 17, 2016 at 8:45 AM, Bernd Helmle <mailings@oopsware.de> wrote:
> Current PostgreSQL Documentation on recovery.conf has this about
> recovery_min_apply_delay[1]:
>
> ---<---
>
> This parameter is intended for use with streaming replication deployments;
> however, if the parameter is specified it will be honored in all cases.
> Synchronous replication is not affected by this setting because there is
> not yet any setting to request synchronous apply of transaction commits.
>
> --->---
>
> If i understand correctly, this is not true anymore with 9.6, where
> remote_apply will have exactly the behavior the paragraph above wants to
> contradict: any transaction executed with synchronous_commit=remote_apply
> will wait at least recovery_min_apply_delay to finish. Given that
> synchronous_commit can be controlled by any user, this might be dangerous
> if someone doesn't take care enough.

Yes, I missed that sentence.  Thanks.

> I think we need a doc patch for that at least, see attached patch against
> master, but 9.6 should have a corrected one, too.

+1

-- 
Thomas Munro
http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Reminder: Call for Papers -- PGDay Austin 2016
Next
From: Michael Paquier
Date:
Subject: Re: WIP: About CMake v2