| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Multiple table synchronizations are processed serially |
| Date: | 2017-05-19 19:47:55 |
| Message-ID: | 7d8033f5-87ae-da85-4f06-8df8747d87e5@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-05-19 19:53:35 | Precision and rounding fixes for money type |
| Previous Message | Robert Haas | 2017-05-19 19:39:44 | Re: [bug fix] PG10: libpq doesn't connect to alternative hosts when some errors occur |