| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Marko Kreen <markokr(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: ecdh support causes unnecessary roundtrips |
| Date: | 2026-02-20 19:17:42 |
| Message-ID: | 2924925.1771615062@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> On 20 Feb 2026, at 17:07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'd rather test the normal configuration
>> normally and make people who want to run the test on a FIPS platform
>> do something different.
> How about a function in Cluster.pm which returns whether the underlying OpenSSL
> is using FIPS or not, and if it does we adjust the config to make it not fail
> on an unallowed group? That way we can have a CI job that runs with FIPS and
> the adjusted test config, and the rest - along with the Buildfarm - runs the
> default config.
If we can get that information easily, then sure.
BTW, I think we should be back-patching these fixes into v18, since
the testing hazard exists there too. But maybe wait till after the
re-release is finished.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-02-20 20:33:06 | Release notes for next week's re-releases |
| Previous Message | Nathan Bossart | 2026-02-20 18:37:45 | Re: Discrepancy in --no-tablespaces behavior between Tar and Plain-text formats |