From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Amit Kapila <akapila@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add wait_for_subscription_sync for TAP tests.
Date: Wed, 03 Aug 2022 10:02:23 -0400
Message-ID: <2966703.1659535343@sss.pgh.pa.us> (raw)
In-Reply-To: <CAA4eK1+ZE8QTkwZyqRf1muMrQeHSa3O3VPbcJTdQcTnUoPbFQA@mail.gmail.com>
References: <E1oJBIf-0006sw-SA@gemulon.postgresql.org>
<20220803104544.k2luy5hr2ugnhgr2@alvherre.pgsql>
<CAA4eK1+ZE8QTkwZyqRf1muMrQeHSa3O3VPbcJTdQcTnUoPbFQA@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, amit.kapila16@gmail.com, alvherre@alvh.no-ip.org, akapila@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add wait_for_subscription_sync for TAP tests.
In-Reply-To: <2966703.1659535343@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox