Re: src/test/subscription/t/005_encoding.pl is broken
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Andres Freund <andres@anarazel.de>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-09-19T15:33:30Z
Lists: pgsql-hackers
Michael Paquier <michael.paquier@gmail.com> writes: > Now, I just had a look at the logs for a failure and a success, and > one difference can be seen in the subscriber's logs as follows: > -LOG: logical replication table synchronization worker for > subscription "mysub", table "test1" has started > -LOG: logical replication table synchronization worker for > subscription "mysub", table "test1" has finished > +WARNING: out of background worker slots > +HINT: You might need to increase max_worker_processes. > The "+" portion is for a failure, and I think that this causes the > subscription to not consume the changes from the publisher which > explains the failure in the test as the logical worker applying the > changes on the subscriber-side is not here. That would indicate that something isn't ever retrying the worker start; but if that's the case, how is it that we get through the other subscription tests with my random-failure patch in place? regards, tom lane
Commits
-
Fix instability in subscription regression test.
- ee266774454d 10.0 landed
- 4939488af9b8 11.0 landed