| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Superuser can permit passwordless connections on postgres_fdw |
| Date: | 2019-12-25 02:25:54 |
| Message-ID: | 20191225022554.GE3448@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-12-25 06:17:22 | Re: pgsql: Fix compiler warning for ppoll() on Cygwin |
| Previous Message | Michael Paquier | 2019-12-25 01:25:49 | pgsql: Rename files and headers related to index AM |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-12-25 02:31:27 | Re: Server crash with Master-Slave configuration. |
| Previous Message | Masahiko Sawada | 2019-12-25 02:23:50 | Re: Online checksums verification in the backend |