Blind attempt to fix SSPI-auth case in 010_dump_connstr.pl.
Tom Lane <tgl@sss.pgh.pa.us>
Blind attempt to fix SSPI-auth case in 010_dump_connstr.pl. Up to now, pg_regress --config-auth had a hard-wired assumption that the target cluster uses the default bootstrap superuser name. pg_dump's 010_dump_connstr.pl TAP test uses non-default superuser names, and was klugily getting around the restriction by listing the desired superuser name as a role to "create". This is pretty confusing (or at least, it confused me). Let's make it clearer by allowing --config-auth mode to be told the bootstrap superuser name. Repurpose the existing --user switch for that, since it has no other function in --config-auth mode. Per buildfarm. I don't have an environment at hand in which I can test this fix, but the buildfarm should soon show if it works. Discussion: https://postgr.es/m/3142.1561840611@sss.pgh.pa.us
Files
| Path | Change | +/− |
|---|---|---|
| src/bin/pg_dump/t/010_dump_connstr.pl | modified | +9 −6 |
| src/test/regress/pg_regress.c | modified | +24 −14 |
Discussion
- Where is SSPI auth username determined for TAP tests? 6 messages · 2019-06-29 → 2019-07-04