From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Kapila <amit.kapila16@gmail.com>
cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
        Amit Kapila <akapila@postgresql.org>,
        pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add wait_for_subscription_sync for TAP tests.
In-reply-to: 
 <CAA4eK1+ZE8QTkwZyqRf1muMrQeHSa3O3VPbcJTdQcTnUoPbFQA@mail.gmail.com>
References: <E1oJBIf-0006sw-SA@gemulon.postgresql.org>
 <20220803104544.k2luy5hr2ugnhgr2@alvherre.pgsql>
 <CAA4eK1+ZE8QTkwZyqRf1muMrQeHSa3O3VPbcJTdQcTnUoPbFQA@mail.gmail.com>
Comments: In-reply-to Amit Kapila <amit.kapila16@gmail.com>
	message dated "Wed, 03 Aug 2022 16:55:37 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2966702.1659535343.1@sss.pgh.pa.us>
Date: Wed, 03 Aug 2022 10:02:23 -0400
Message-ID: <2966703.1659535343@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2966703.1659535343%40sss.pgh.pa.us>
Precedence: bulk

Amit Kapila <amit.kapila16@gmail.com> writes:
> Yeah, that can happen for bug fixes but may not be a big problem as it
> just avoids duplicate code. If you and others want we can back this
> now or otherwise, we can do it later if we really see the difficulty
> later.

IMO we've seldom regretted back-patching testing infrastructure.
We have regretted not doing so.

			regards, tom lane