Re: contrib/sepgsql regression tests have been broken for months

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: contrib/sepgsql regression tests have been broken for months
Date: 2025-10-31 19:48:14
Message-ID: 3861765.1761940094@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joe Conway <mail(at)joeconway(dot)com> writes:
> On 10/29/25 19:36, Tom Lane wrote:
>> ... I think the new idea
>> is to leave the module installed and active, which is kind
>> of problematic if we want to also use TestSepgsql.pm in the
>> back branches.

> I suppose one solution is to create a new buildfarm animal and then use
> rhino only for <= pg17 and <rhino-prime> only for pg18+

It looks like it'd work to revert to using TestSepgsql.pm in all
branches. You'd need to remove 'sepgsql' from PG_TEST_EXTRA so
that v18/master don't try to run the conflicting 001_sepgsql.pl
tests.

We need a better idea about how the new test method can coexist
with the old one, but for now I'd just like rhino to be running
one or the other successfully ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2025-10-31 19:59:20 Re: Remaining dependency on setlocale()
Previous Message Euler Taveira 2025-10-31 19:46:14 Re: [PATCH] Add Windows support for backtrace_functions (MSVC only)