Re: Remove backend warnings from SSL tests

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Subject: Re: Remove backend warnings from SSL tests
Date: 2023-07-19 14:22:56
Message-ID: 240205.1689776576@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Aleksander Alekseev <aleksander(at)timescale(dot)com> writes:
>> Alternatively we could get rid of
>> ENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS entirely since its practical
>> value seems to be debatable.

> Strong -1 on that, for the reason given above.

Perhaps an alternative could be to expend some more sweat on the
mechanism, so that it's actually enforced (with ERROR) during
"make installcheck", but not in "make check" or TAP tests?
I'm not sure how to make that work exactly.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2023-07-19 14:46:52 Re: Let's make PostgreSQL multi-threaded
Previous Message Hayato Kuroda (Fujitsu) 2023-07-19 14:03:22 RE: [PoC] pg_upgrade: allow to upgrade publisher node