| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com>, Greg Nancarrow <gregn4422(at)gmail(dot)com>, Ajin Cherian <itsajin(at)gmail(dot)com>, "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Subject: | Re: Added schema level support for publication. |
| Date: | 2021-08-12 04:55:20 |
| Message-ID: | CAA4eK1KqhUBHbcpT92VMPvUUDgGvyOK0ekXOwjNR6L=Y_bcsGw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 11, 2021 at 7:45 PM Mark Dilger
<mark(dot)dilger(at)enterprisedb(dot)com> wrote:
>
> > On Aug 10, 2021, at 10:59 PM, vignesh C <vignesh21(at)gmail(dot)com> wrote:
> >
> > Also, the behavior of "Alter publication drop table" for which the
> > user is not the owner is successful, Is this behavior correct?
>
> I think that dropping a table from a publication should be allowed for the publication owner, without regard to the owner of the table.
> Adding a table to a publication is different, as it exposes the contents of the table.
>
..
..
>
> Clearly user2 cannot modify pub1, not even with respect to user2's own table. user1 can modify its own publication except for adding someone else's table. This seems correct to me.
>
That looks reasonable to me as well and I think we should follow the
same for the schema.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2021-08-12 05:25:55 | Re: call popcount32/64 directly on non-x86 platforms |
| Previous Message | Amit Kapila | 2021-08-12 04:22:18 | Re: Next Steps with Hash Indexes |