Request a Demo
Home   >   mailing lists

Re: Improve documentation of publication privilege checks - Mailing list pgsql-hackers

From Peter Smith
Subject Re: Improve documentation of publication privilege checks
Date
Msg-id CAHut+PvombcsmxHgAe-WzjBqNdAr9REePP=xXM_cvd_nS5C-dA@mail.gmail.com
Whole thread Raw
In response to Re: Improve documentation of publication privilege checks  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: Improve documentation of publication privilege checks
List pgsql-hackers
Tree view 
Hi Shlok/Chao-San.

How about this alternative wording:

  <para>
   To create a publication using any of <literal>FOR ALL TABLES</literal>,
   <literal>FOR ALL SEQUENCES</literal>, or
   <literal>FOR TABLES IN SCHEMA</literal>, the user must be a superuser.
   To alter a publication using <literal>ADD TABLE</literal>, the user must
   have ownership rights on the table.  To alter a publication using
   <literal>ADD TABLES IN SCHEMA</literal>, the user must be a superuser.
  </para>


IMO this is both simpler and more consistent. PSA a diff for the same.

======
Kind Regards,
Peter Smith.
Fujitsu Australia
Attachment

pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: DOCS - "\d mytable" also shows any publications that publish mytable
Next
From: Chao Li
Date:
Subject: Re: Fix wrong reference in pg_overexplain's doc