| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Greg Clough <greg(at)gclough(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: BUG #13770: Extending recovery_min_apply_delay on Standby causes it to be unavailable for a while |
| Date: | 2016-01-10 23:21:23 |
| Message-ID: | CAB7nPqT=cD80Z5eby_t7SJsdtEq8_ZEnMBuVBBzX=6xb5yE=2A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Jan 2, 2016 at 9:14 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2016-01-11 16:42:45 | Re: BUG #13855: After pg_dump, pg_restore complains that some data is too long |
| Previous Message | igal | 2016-01-10 18:23:01 | BUG #13859: pg_upgrade permissions on Windows |