| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Petr Jelinek <petr(dot)jelinek(at)enterprisedb(dot)com> |
| Subject: | Re: Why does the owner of a publication need CREATE privileges on the database? |
| Date: | 2021-08-10 06:15:09 |
| Message-ID: | CAA4eK1L036o=ddArFrPNv0W20XM1hxRK1vynW=c_S0S9p7_ezw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 27, 2021 at 11:29 PM Mark Dilger
<mark(dot)dilger(at)enterprisedb(dot)com> wrote:
>
> The documentation for ALTER PUBLICATION ... OWNER TO ... claims the new owner must have CREATE privilege on the database, though superuser can change the ownership in spite of this restriction. No explanation is given for this requirement.
>
I am not aware of the original thought process behind this but current
behavior seems reasonable because if users need to have CREATE
privilege on the database while Create Publication, the same should be
true while we change the owner to a new owner. Basically, at any point
in time, the owner of the publication should have CREATE privilege on
the database which contains the publication.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-08-10 06:20:50 | Re: ECPG bug fix: DECALRE STATEMENT and DEALLOCATE, DESCRIBE |
| Previous Message | Amit Kapila | 2021-08-10 05:37:14 | Re: Added schema level support for publication. |