=?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= writes:
> On Sat, May 10, 2014 at 5:22 PM, Robert Haas wrote:
>> On Fri, May 9, 2014 at 10:44 PM, FabrÃzio de Royes Mello
>> wrote:
Wouldn't a better name be recovery_min_apply_delay?
>>> +1
>> Works for me.
> Done!!
Since there were no objectio
On Sat, May 10, 2014 at 5:22 PM, Robert Haas wrote:
>
> On Fri, May 9, 2014 at 10:44 PM, Fabrízio de Royes Mello
> wrote:
> >> Wouldn't a better name be recovery_min_apply_delay?
> >
> > +1
>
> Works for me.
>
Done!!
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://
On Fri, May 9, 2014 at 10:44 PM, Fabrízio de Royes Mello
wrote:
>> Wouldn't a better name be recovery_min_apply_delay?
>
> +1
Works for me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgre
Em sexta-feira, 9 de maio de 2014, Peter Eisentraut
escreveu:
> Wouldn't a better name be recovery_min_apply_delay?
>
>
+1
The original name was recovery_apply_delay but in some point of review it
was changed to reflect better the limit.
> Other parameters are usually named something_min_somet
Wouldn't a better name be recovery_min_apply_delay?
Other parameters are usually named something_min_something.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers