Re: Replication & recovery_min_apply_delay - Mailing list pgsql-hackers

From Asim Rama Praveen
Subject Re: Replication & recovery_min_apply_delay
Date
Msg-id 158012525598.742.4628546558494254315.pgcf@coridan.postgresql.org
Whole thread Raw
In response to Re: Replication & recovery_min_apply_delay  (Asim R P <apraveen@pivotal.io>)
Responses Re: Replication & recovery_min_apply_delay  (Asim R P <apraveen@pivotal.io>)
List pgsql-hackers
The following review has been posted through the commitfest application:
make installcheck-world:  not tested
Implements feature:       not tested
Spec compliant:           not tested
Documentation:            not tested

The logic to start WAL receiver early should not be coupled with recovery_min_apply_delay GUC.  WAL receiver's delayed
startaffects replication in general, even when the GUC is not set.
 

A better fix would be to start WAL receiver in the main replay loop, as soon as consistent state has been reached.

As noted during previous reviews, scanning all WAL just to determine streaming start point seems slow.  A faster
solutionseems desirable. 

The new status of this patch is: Waiting on Author

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pause recovery if pitr target not reached
Next
From: Asim R P
Date:
Subject: Re: Replication & recovery_min_apply_delay