Re: Patch: doc for pg_logical_emit_message()
Fujii Masao <masao.fujii@gmail.com>
From: Fujii Masao <masao.fujii@gmail.com>
To: "Matsumura, Ryo" <matsumura.ryo@jp.fujitsu.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2019-04-24T14:39:32Z
Lists: pgsql-hackers
On Wed, Apr 24, 2019 at 11:12 AM Matsumura, Ryo <matsumura.ryo@jp.fujitsu.com> wrote: > > On Tue. Apr. 23, 2019 at 02:59 AM Masao, Fujii > <masao.fujii@gmail.com> wrote: > > Thank you for the comment. > > > So I think that the patch should fix also the description for those > > replication functions. Thought? > > I think so too. > I attach a new patch. Thanks for updating the patch! + Use of functions for replication origin is restricted to superusers. + Use of functions for replication slot is restricted to superusers and replication roles. "replication role" is a bit confusing. For example, we have "replication role" related to session_replication_role. So I think it's better to use something like "users having <literal>REPLICATION</literal> privilege". + Only <function>pg_logical_emit_message</function> can be used by any users. Not any user, I think. For example, what about a user not having EXECUTE privilege on pg_logical_emit_message function? I don't think that this description only for pg_logical_emit_message is necessary. Regards, -- Fujii Masao
Commits
-
Fix documentation for the privileges required for replication functions.
- bc250ee7ebd0 9.4.23 landed
- 2be2fee24839 9.5.18 landed
- 44b973b71c95 9.6.14 landed
- 704637d8d935 10.9 landed
- a9d5383db2e1 11.4 landed
- df631ebc737e 12.0 landed