| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: subscription worker doesn't start immediately on eabled |
| Date: | 2017-04-21 14:15:20 |
| Message-ID: | 77f75a90-a495-6661-68df-e4993bfac3e3@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/6/17 08:24, Kyotaro HORIGUCHI wrote:
> Hello. I found dubious behavior while playing with logical
> replication.
>
> When we disable a subscription, replication worker immediately stops.
>
> =# ALTER SUBSCRIPTION s1 DISABLE;
>
> On the other hand even if we enable a subscription, worker
> doesn't start immediately. It takes 3 minutes in the worst
> case. (DEFAULT_NAPTIME_PER_CYCLE)
>
> The attached patch wakes up launcher when a subscription is
> enabled. This fails when a subscription is enabled immedaitely
> after disabling but it won't be a matter.
What do you mean by "this fails"?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-04-21 14:19:34 | Re: Interval for launching the table sync worker |
| Previous Message | Petr Jelinek | 2017-04-21 14:11:36 | Re: tablesync patch broke the assumption that logical rep depends on? |