Postgres Pro
Downloads
Home   >   mailing lists

Re: recovery_min_apply_delay in archive recovery causes assertionfailure in latch - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: recovery_min_apply_delay in archive recovery causes assertionfailure in latch
Date
Msg-id 20191019022859.GC1542@paquier.xyz
Whole thread Raw
In response to Re: recovery_min_apply_delay in archive recovery causes assertionfailure in latch  (Michael Paquier <michael@paquier.xyz>)
Responses Re: recovery_min_apply_delay in archive recovery causes assertionfailure in latch
List pgsql-hackers
Tree view 
On Thu, Oct 17, 2019 at 02:35:13PM +0900, Michael Paquier wrote:
> ArchiveRecoveryRequested will be set to true if recovery.signal or
> standby.signal are found, so it seems to me that you can make all
> those checks more simple by removing from the equation
> StandbyModeRequested, no?  StandbyModeRequested is never set to true
> if ArchiveRecoveryRequested is not itself true.

For the sake of the archives, this has been applied by Fujii-san as of
ec1259e8.
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Remaining calls of heap_close/heap_open in the tree
Next
From: Michael Paquier
Date:
Subject: Re: Backport "WITH ... AS MATERIALIZED" syntax to <12?