Re: Recognizing superuser in pg_hba.conf

Поиск
Список
Период
Сортировка
От Daniel Gustafsson
Тема Re: Recognizing superuser in pg_hba.conf
Дата
Msg-id 7EE797B4-0FF3-43B6-AAE4-E33F8568F66C@yesql.se
обсуждение исходный текст
Ответ на Re: Recognizing superuser in pg_hba.conf  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Recognizing superuser in pg_hba.conf  (Vik Fearing <vik@postgresfriends.org>)
Список pgsql-hackers
> On 30 Mar 2020, at 20:28, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:
>> I see this patch is marked as RFC since 12/30, but there seems to be
>> quite a lot of discussion about the syntax, keywords and how exactly to
>> identify the superuser. So I'll switch it back to needs review, which I
>> think is a better representation of the current state.
>
> Somebody switched it to RFC again, despite the facts that
>
> (a) there is absolutely no consensus about what syntax to use
> (and some of the proposals imply very different patches),
>
> (b) there's been no discussion at all since the last CF, and
>
> (c) the patch is still failing in the cfbot (src/test/ssl fails).
>
> While resolving (c) would seem to be the author's problem, I don't
> think it's worth putting effort into that detail until we have
> some meeting of the minds about (a).  So I'll put this back to
> "needs review".

Since there hasn't been any more progress on this since the last CF, and the
fact that the outcome may result in a completely different patch, I'm inclined
to mark this returned with feedback rather than have it linger.  The discussion
can continue and the entry be re-opened.

Thoughts?

cheers ./daniel


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

Предыдущее
От: Daniel Gustafsson
Дата:
Сообщение: Re: Read access for pg_monitor to pg_replication_origin_status view
Следующее
От: Vik Fearing
Дата:
Сообщение: Re: Recognizing superuser in pg_hba.conf