On 5/19/17 01:01, Masahiko Sawada wrote:
> Seems all four table sync workers are launched at the almost same
> time, but three workers of them get stuck in idle transaction state
> when creating replication slot. That is these waiting workers cannot
> proceed its work until first connected table sync worker finishes. ps
> command shows the followings.
Creating a replication slot waits for all transactions to finish. So if
one of those transactions is a table copy of another subscription, it
has to wait for that.
You can avoid that by creating all the slots first and then triggering
the initial table copy separately.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
