Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joe Conway <mail@joeconway.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, Jacob Champion <jacob.champion@enterprisedb.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-10-31T19:48:14Z
Lists: pgsql-hackers 
Joe Conway <mail@joeconway.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

Commits

  1. Update expected output for contrib/sepgsql's regression tests.

  2. Print out error position for some ALTER TABLE ALTER COLUMN type