Re: BUG #17670: Logical Replication data may be lost on the subscription under certain scenarios

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: Japin Li <japinli(at)hotmail(dot)com>
Cc: xyh(at)nvn(dot)xyz, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17670: Logical Replication data may be lost on the subscription under certain scenarios
Date: 2022-10-31 08:53:46
Message-ID: CAFiTN-tknTS_94LbagQm451SgtLQcNQzUtkbo6EcrJL4T3Y1NQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Oct 30, 2022 at 7:22 PM Japin Li <japinli(at)hotmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kieran McCusker 2022-10-31 10:07:02 Re: BUG #17671: Query returns unexpected result
Previous Message PG Bug reporting form 2022-10-31 08:42:34 BUG #17673: Regression tests failed with llvm 11+ when using address sanitizers