On Wed, Sep 20, 2017 at 12:33 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > 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?
I have been able to dig into this issue further, and the problem is indeed in the wait logic of 005_encoding.pl. It is important to wait for the initial sync of the subscriber to happen. There is no need to incorporate the additional wait query in wait_for_caught_up() as well. Please see the attached which fixes the stability problems for me even after forcing failures in launcher.c. -- Michael
tap-subs-encoding.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
