On Fri, Oct 28, 2022 at 8:07 PM Japin Li <japinli@hotmail.com> wrote:
> I can reproduce it on HEAD. Here is my analysis:
>
> When we rename the t_test1 to t_test2, the subscriber doesn't have a
> table matched publication table name, so the logical replication throw
> an error. Then, we create a new t_test1 on subscriber, the logical
> replication worker can find the table that matches the published name.
> However, the pg_subscription_rel hasn't updated, and when we try to get
> the subscription state through GetSubscriptionRelState(), it cannot find
> a matched subscription relation mapping, so the WAL cannot apply to the
> new table t_test1.
I am just wondering if it is correct behavior to allow renaming the
table used by a subscription, or should there be some dependency?
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com