Re: [16+] subscription can end up in inconsistent state
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-bugs@postgresql.org, Robert Haas <robertmhaas@gmail.com>
Date: 2023-09-13T04:51:11Z
Lists: 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.
Commits
-
Fix buildfarm error from commit 5c31669058.
- 5b5318c38745 16.2 landed
- dd3ca8cbb014 17.0 landed
-
Re-validate connection string in libpqrcv_connect().
- 4c03ac7e2bc4 16.2 landed
- 5c31669058b5 17.0 landed