| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Greg Nancarrow <gregn4422(at)gmail(dot)com>, "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, Alexey Lesovsky <lesovsky(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "osumi(dot)takamichi(at)fujitsu(dot)com" <osumi(dot)takamichi(at)fujitsu(dot)com> |
| Subject: | Re: Skipping logical replication transactions on subscriber side |
| Date: | 2022-01-24 14:06:11 |
| Message-ID: | 31d57a2e-437c-e584-d1e0-27063410bd63@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22.01.22 03:54, Amit Kapila wrote:
> Won't we already do that for Alter Subscription command which means
> nothing special needs to be done for this? However, it seems to me
> that the idea we are trying to follow here is that as this option can
> lead to data inconsistency, it is good to allow only superusers to
> specify this option. The owner of the subscription can be changed to
> non-superuser as well in which case I think it won't be a good idea to
> allow this option. OTOH, if we think it is okay to allow such an
> option to users that don't have superuser privilege then I think
> allowing it to the owner of the subscription makes sense to me.
I don't think this functionality allows a nonprivileged user to do
anything they couldn't otherwise do. You can create inconsistent data
in the sense that you can choose not to apply certain replicated data.
But a subscription owner has to have write access to the target tables
of the subscription, so they already have the ability to write or not
write any data they want.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-01-24 14:10:35 | Re: Skipping logical replication transactions on subscriber side |
| Previous Message | Yura Sokolov | 2022-01-24 13:24:29 | Re: Fix BUG #17335: Duplicate result rows in Gather node |