| From: | Petr Jelinek <petr(dot)jelinek(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-06 16:33:43 |
| Message-ID: | 222fb4e5-acb8-cc4d-fb7b-3d12740512b4@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06/04/17 14: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.
>
Makes sense, I think this got lost in all the refactoring, thanks.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-04-06 16:34:32 | Re: pg_background contrib module proposal |
| Previous Message | Jim Nasby | 2017-04-06 16:14:43 | Re: Faster methods for getting SPI results (460% improvement) |