Re: pgsql: Superuser can permit passwordless connections on postgres_fdw - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pgsql: Superuser can permit passwordless connections on postgres_fdw
Date
Msg-id CAA8=A7-BHHo-3Jd9bfa1M8ARZZkwv4ZafwXeS6ZVGoKx8MV62w@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Superuser can permit passwordless connections onpostgres_fdw  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pgsql: Superuser can permit passwordless connections on postgres_fdw  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Dec 25, 2019 at 12:56 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Fri, Dec 20, 2019 at 10:17:20PM -0500, Tom Lane wrote:
> > Yeah, it's sort of annoying that the buildfarm didn't notice this
> > aspect of things.  I'm not sure I want to spend cycles on checking
> > it in every test run, though.
> >
> > Maybe we could have -DENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS
> > enable a check for that aspect along with what it does now?
>
> Makes sense to restrict that under the flag.  Perhaps a catalog scan
> of pg_authid at the end of pg_regress and isolationtester then?


What's the preferred way to set that?

"configure CPPFLAGS=-DENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS"?

Maybe I should add that to the sample buildfarm config ...

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Libpq support to connect to standby server as priority
Next
From: Maciek Sakrejda
Date:
Subject: Re: Duplicate Workers entries in some EXPLAIN plans