RE: pg_replication_origin_session_setup and superuser

Поиск
Список
Период
Сортировка
От Zohar Gofer
Тема RE: pg_replication_origin_session_setup and superuser
Дата
Msg-id VI1PR06MB508654AFFB6F55AA6258A6979B879@VI1PR06MB5086.eurprd06.prod.outlook.com
обсуждение исходный текст
Ответ на Re: pg_replication_origin_session_setup and superuser  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
Thanks. This seems to be the fix we need.
Would it be possible to push it to previous versions? 12 or 13?

Zohar

-----Original Message-----
From: Michael Paquier <michael@paquier.xyz>
Sent: Tuesday, February 16, 2021 2:52 AM
To: Zohar Gofer <Zohar.Gofer@amdocs.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: pg_replication_origin_session_setup and superuser

On Mon, Feb 15, 2021 at 09:37:53AM +0000, Zohar Gofer wrote:
> In my mind the requirement for superuser is too strong. I think that
> requiring privileges of a replication user is more suitable. This way
> we can require that only a user with replication privileges will
> actually do replication, even if this is not really a replication.

PostgreSQL 14 will remove those hardcoded superuser checks.  Please see this thread:
https://www.postgresql.org/message-id/CAPdiE1xJMZOKQL3dgHMUrPqysZkgwzSMXETfKkHYnBAB7-0VRQ@mail.gmail.com
And its related commit:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=cc072641d41c55c6aa24a331fc1f8029e0a8d799

While the default is still superuser-only, it becomes possible to grant access to this stuff to other roles that have
noneed to be superusers. 
--
Michael
This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms
ofService, which you may review at https://www.amdocs.com/about/email-terms-of-service
<https://www.amdocs.com/about/email-terms-of-service>




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

Предыдущее
От: Amit Langote
Дата:
Сообщение: Re: A reloption for partitioned tables - parallel_workers
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: adding wait_start column to pg_locks