Re: [HACKERS] Logical replication launcher useswal_retrieve_retry_interval - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Logical replication launcher useswal_retrieve_retry_interval
Date
Msg-id aaa39cfa-b94b-643a-b06c-de02e4905608@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Logical replication launcher uses wal_retrieve_retry_interval  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: [HACKERS] Logical replication launcher useswal_retrieve_retry_interval  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
List pgsql-hackers
On 4/16/17 22:40, Masahiko Sawada wrote:
> Attached two patches add new GUCs apply_worker_timeout and
> apply_worker_launch_interval which are used instead of
> wal_receiver_timeout and wal_retrieve_retry_timeout. These new
> parameters are not settable at worker-level so far.

Under what circumstances are these needed?  Does anyone ever set these?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Inadequate parallel-safety check for SubPlans
Next
From: Remi Colinet
Date:
Subject: Re: [HACKERS] [PATCH] New command to monitor progression of longrunning queries