After renaming a database the subscription ( logical replication) stay sticky to the old database (master)

From: Mai Peng <maily(dot)peng(at)webedia-group(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Cc: Yannick Le Guédart <yannick(dot)le-guedart(at)webedia-group(dot)com>
Subject: After renaming a database the subscription ( logical replication) stay sticky to the old database (master)
Date: 2020-06-29 12:58:32
Message-ID: B62A5C5C-A627-487D-A132-930873704E30@webedia-group.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello,
I restored the production database to staging environment, then dropped the publication on old database, dropped the subscription on the slave.
I have to rename the old database in order to keep an old version of data. When I re-add the subscription logical replication, pointing to the new database, the slave still want to synchronize to the old database ( renamed) and the accumulated WAL files are crashing the filesystem.
How can I handle the problem ?
Thank you

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Ribe 2020-06-29 16:22:10 pg_basebackup compression
Previous Message Thomas Kellerer 2020-06-25 18:17:47 Re: using regular expression queries with regular expression indexes