Re: BUG #17670: Logical Replication data may be lost on the subscription under certain scenarios - Mailing list pgsql-bugs

From Dilip Kumar
Subject Re: BUG #17670: Logical Replication data may be lost on the subscription under certain scenarios
Date
Msg-id CAFiTN-tknTS_94LbagQm451SgtLQcNQzUtkbo6EcrJL4T3Y1NQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17670: Logical Replication data may be lost on the subscription under certain scenarios  (Japin Li <japinli@hotmail.com>)
Responses Re: BUG #17670: Logical Replication data may be lost on the subscription under certain scenarios
List pgsql-bugs
On Sun, Oct 30, 2022 at 7:22 PM Japin Li <japinli@hotmail.com> wrote:

> > I am just wondering if it is correct behavior to allow renaming the
> > table used by a subscription, or should there be some dependency?
>
> Maybe we can add a dependency to make the user know what they are doing.
> I also want to know when we should add a dependency?

I haven't thought about it in deep, but I think whenever we add a new
entry to pg_subscription_rel, that time maybe we could add a
dependency on the respective subscription entry IMHO.  But I am just
wondering is there any reason why we are not already having such
dependency?

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17673: Regression tests failed with llvm 11+ when using address sanitizers
Next
From: Kieran McCusker
Date:
Subject: Re: BUG #17671: Query returns unexpected result