Re: Patch: doc for pg_logical_emit_message() - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Patch: doc for pg_logical_emit_message()
Date
Msg-id CAHGQGwGB11ytJT0OGaHr3i2C81mWCXjC+YUvj4u-zUNRMjQXtQ@mail.gmail.com
Whole thread Raw
In response to RE: Patch: doc for pg_logical_emit_message()  ("Matsumura, Ryo" <matsumura.ryo@jp.fujitsu.com>)
Responses RE: Patch: doc for pg_logical_emit_message()
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [Patch] Check file type before calling AllocateFile() for files out of pg data directory to avoid potential issues (e.g. hang).
Next
From: Antonin Houska
Date:
Subject: Re: "WIP: Data at rest encryption" patch and, PostgreSQL 11-beta3