Re: Patch: doc for pg_logical_emit_message()

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: "Matsumura, Ryo" <matsumura(dot)ryo(at)jp(dot)fujitsu(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch: doc for pg_logical_emit_message()
Date: 2019-04-22 17:59:02
Message-ID: CAHGQGwH9Qv=pdyZV4vXjy72940Hpkea3SPiQg1Mxaytfw03RmQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 19, 2019 at 3:21 PM Matsumura, Ryo
<matsumura(dot)ryo(at)jp(dot)fujitsu(dot)com> wrote:
>
> Hi, Hackers
>
> pg_logical_emit_message() can be used by any user,
> but the following document says that it can be used by only superuser.
>
> > Table 9.88. Replication SQL Functions
> > Use of these functions is restricted to superusers.
>
> I think that pg_logicl_emit_message() should be used by any user.
> Therefore, I attach the document patch.

Thanks for the patch!

Use of not only pg_logical_emit_message() but also other replication
functions in Table 9.88 is not restricted to superuser. For example,
replication role can execute pg_create_physical_replication_slot().
So I think that the patch should fix also the description for those
replication functions. Thought?

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2019-04-22 18:03:41 Re: block-level incremental backup
Previous Message Andres Freund 2019-04-22 17:55:47 Re: clean up docs for v12