Re: BUG #13770: Extending recovery_min_apply_delay on Standby causes it to be unavailable for a while

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-03-04 02:57:13
Message-ID: CAB7nPqStx0LJKUu1=3MX4xeVP+NLxBzmKs-wUocuyJqUA8SOTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Mar 4, 2016 at 2:35 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2016-03-03 23:42:25 +0900, Fujii Masao wrote:
>> We should backpatch this? I'm tempted to do that
>> because it seems an oversight.
>> It's user-visible change of behavior, though.
>
> I agree we should.

We definitely need to backpatch.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Felix Ostmann 2016-03-04 06:56:23 pg_dump ignore CASTs when using --schema
Previous Message rsimeon 2016-03-03 23:38:59 BUG #13999: pg_upgrade failing with FATAL: unrecognized configuration parameter "unix_socket_directory"