backpatch tests: Rename conflicting role names to 14/15

On Wed, Dec 10, 2025 at 04:39:11PM -0600, Sami Imseih wrote:

On 15 STABLE, I encountered the same issue [0] which was fixed in 6a20b04f0408
starting from 16. It seems like a decision not to backpatch to lower
versions at the time was due to a lack of reports [1], but I think since we have to
support 14 and 15 for a few more years, it makes sense to.

The issue is that Sami has been able to trigger this problem
internally. :)

I can prepare the patches if there are no objections.

If you could prepare a patch, that would be great! Let's do that if
v14 and v15 can also face the issue under a high-concurrent build.
The blast area of 6a20b04f0408 is not that bad.
--
Michael

I can prepare the patches if there are no objections.

If you could prepare a patch, that would be great! Let's do that if
v14 and v15 can also face the issue under a high-concurrent build.
The blast area of 6a20b04f0408 is not that bad.

"make-installcheck --jobs 8" has reproduced the conflict almost
consistently between adminpack and plperl tests.

cherry-pick to 15 had no conflicts. 14 does not have the
plperl_setup_scratch schema, so I had to fix that.

See the attached.

--
Sami Imseih
Amazon Web Services

On Wed, Dec 10, 2025 at 06:57:56PM -0600, Sami Imseih wrote:

"make-installcheck --jobs 8" has reproduced the conflict almost
consistently between adminpack and plperl tests.

cherry-pick to 15 had no conflicts. 14 does not have the
plperl_setup_scratch schema, so I had to fix that.

See the attached.

Thanks for the patches. These look correct, so applied to v15 and
v14.
--
Michael