Re: Where is SSPI auth username determined for TAP tests?

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Where is SSPI auth username determined for TAP tests?
Дата
Msg-id 20190703062024.GD3084@paquier.xyz
обсуждение исходный текст
Ответ на Re: Where is SSPI auth username determined for TAP tests?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Where is SSPI auth username determined for TAP tests?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Sun, Jun 30, 2019 at 12:09:18PM -0400, Tom Lane wrote:
> We could apply the same hack on the source node, but I wonder if it
> wouldn't be better to make this less of a kluge.  I'm tempted to
> propose that "pg_regress --config-auth --user XXX" should understand
> XXX as the bootstrap superuser name, and then we could clean up
> 010_dump_connstr.pl by using that.

I have been reviewing that part, and the part to split the bootstrap
user from the set of extra roles created looks fine to me.  Now, it
seems to me that you can simplify 010_dump_connstr.pl as per the
attached because PostgresNode::Init can take care of --auth-config
part with the correct options using auth_extra.  What do you think
about the cleanup attached?
--
Michael

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Amit Langote
Дата:
Сообщение: Re: Another way to fix inherited UPDATE/DELETE
Следующее
От: Richard Guo
Дата:
Сообщение: Re: [HACKERS] WIP: Aggregation push-down