On 25.01.22 03:54, Amit Kapila wrote:
>> 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.
>>
> I thought this will be the only primary way to skip applying certain
> transactions. The other could be via pg_replication_origin_advance().
> Or are you talking about the case where we skip applying update/delete
> where the corresponding rows are not found?
>
> I see the point that if we can allow the owner to skip applying
> updates/deletes in certain cases then probably this should also be
> okay. Kindly let us know if you have something else in mind as well?
Let's start this again: The question at hand is whether ALTER
SUBSCRIPTION ... SKIP should be allowed for subscription owners that are
not superusers. The argument raised against that was that this would
allow the owner to create "inconsistent" data. But it hasn't been
explained what that actually means or why it is dangerous.
