Re: BUG #13770: Extending recovery_min_apply_delay on Standby causes it to be unavailable for a while - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #13770: Extending recovery_min_apply_delay on Standby causes it to be unavailable for a while
Date
Msg-id CAB7nPqT=cD80Z5eby_t7SJsdtEq8_ZEnMBuVBBzX=6xb5yE=2A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13770: Extending recovery_min_apply_delay on Standby causes it to be unavailable for a while  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
On Sat, Jan 2, 2016 at 9:14 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Changing my mind after more thoughts on the matter, it seems indeed
> that it would make more sense to apply delays only once the database
> has reached a consistent state to be able to do immediately
> transaction-related operations on a standby without having to wait for
> it to reach consistency for perhaps a couple of hours. Please see
> attached a patch to do that.

CF entry added here:
https://commitfest.postgresql.org/9/478/
--
Michael

pgsql-bugs by date:

Previous
From: igal@lucee.org
Date:
Subject: BUG #13859: pg_upgrade permissions on Windows
Next
From: Kevin Grittner
Date:
Subject: Re: BUG #13855: After pg_dump, pg_restore complains that some data is too long