Re: [HACKERS] src/test/subscription/t/005_encoding.pl is broken
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] src/test/subscription/t/005_encoding.pl is broken |
Дата | |
Msg-id | 6768.1505835210@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] src/test/subscription/t/005_encoding.pl is broken (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: [HACKERS] src/test/subscription/t/005_encoding.pl is broken
|
Список | 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: