Re: Recovery test failure for recovery_min_apply_delay on hamster - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Recovery test failure for recovery_min_apply_delay on hamster
Date
Msg-id CAB7nPqSGFpe1q3p3ErnNA6jhaU-DBgmWR_tkkz97CssYURX4fw@mail.gmail.com
Whole thread Raw
In response to Re: Recovery test failure for recovery_min_apply_delay on hamster  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Recovery test failure for recovery_min_apply_delay on hamster
List pgsql-hackers
On Wed, Mar 9, 2016 at 12:14 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Is there anything we can do to short-circuit the wait in the case that
> replication happens promptly?  A one-minute wait would be acceptable we
> terminate it early by checking every second.

After sleeping (best debugger ever) on that, actually a way popped up
in my mind, and I propose the attached, which refactors a bit 005 and
checks that the LSN position of master has been applied on standby
after at least the delay wanted. A maximum delay of 90s is authorized,
like poll_query_until.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Proposal: RETURNING primary_key()
Next
From: Michael Paquier
Date:
Subject: Re: Parallel query fails on standby server