Re: [16+] subscription can end up in inconsistent state - Mailing list pgsql-bugs

From Amit Kapila
Subject Re: [16+] subscription can end up in inconsistent state
Date
Msg-id CAA4eK1LN37r8c6ggiRZhxYg=XjTzztud0+3JiVkgPb8enfqM3A@mail.gmail.com
Whole thread Raw
In response to Re: [16+] subscription can end up in inconsistent state  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-bugs
On Wed, Sep 13, 2023 at 2:04 AM Jeff Davis <pgsql@j-davis.com> wrote:
>
> On Tue, 2023-09-12 at 16:13 +0530, Amit Kapila wrote:
> > Do we want to remove
> > that as anyway, we will do that check via walrcv_connect()?
>
> I think we should keep the DDL-time checks in place as a best-effort,
> but not rely on them for security.
>
> > Another point is that if we want to unify such a check at the time of
> > walrcv_connect() then do we need to do it at the time of Alter
> > Subscription? I think it will probably be better to catch the problem
> > early
>
> Agreed. Catching mistakes at DDL time is a better user experience.
>
> >  but does removing it from Alter Subscription time and doing it
> > at connect time lead to security hazards?
>
> We'd still be doing the same check, just later, right?
>

Right.

--
With Regards,
Amit Kapila.



pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #18046: stats collection behaviour change is affecting the usability of information.
Next
From: 姜梦洋
Date:
Subject: the same time value return different values,is it a problem