Re: recovery_min_apply_delay with a negative value

From: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: recovery_min_apply_delay with a negative value
Date: 2014-12-29 19:30:32
Message-ID: CAFcNs+q9qU+tip8E3f4hBpT1HtUuCvx5Mf2a_w8YSVKXCiVpAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Dec 28, 2014 at 12:31 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:
>
> Hi all,
>
> While reviewing another patch, I have noticed that
recovery_min_apply_delay can have a negative value. And the funny part is
that we actually attempt to apply a delay even in this case, per se this
condition recoveryApplyDelay(at)xlog(dot)c:
> /* nothing to do if no delay configured */
> if (recovery_min_apply_delay == 0)
> return false;
> Shouldn't we simply leave if recovery_min_apply_delay is lower 0, and not
only equal to 0?
>

Seems reasonable.

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2014-12-29 20:07:44 Re: BUG #12330: ACID is broken for unique constraints
Previous Message Tom Lane 2014-12-29 17:55:11 Re: ON_ERROR_ROLLBACK