diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-06-30 13:34:45 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-06-30 13:34:45 -0400 |
| commit | 681cca86f5071379c4a8599ef9387b666b7e6879 (patch) | |
| tree | b29e968e481aee7d4fd8bb01d3b67892ac135d6c /src/backend/utils/adt/oracle_compat.c | |
| parent | c91504b958e1647f87ffb7168e61db75ca09b928 (diff) | |
| download | postgresql-681cca86f5071379c4a8599ef9387b666b7e6879.tar.gz postgresql-681cca86f5071379c4a8599ef9387b666b7e6879.zip | |
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
Diffstat (limited to 'src/backend/utils/adt/oracle_compat.c')
0 files changed, 0 insertions, 0 deletions