From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Mai Peng <maily.peng@webedia-group.com>
To: pgsql-admin@postgresql.org
Cc: Yannick Le Guédart <yannick.le-guedart@webedia-group.com>
Subject: Re: After renaming a database the subscription ( logical replication) stay sticky to the old database (master)
Date: Mon, 29 Jun 2020 19:10:12 +0200
Message-ID: <cbfc0551-0339-2a16-05b1-9a52a4fa4e5c@2ndquadrant.com> (raw)
In-Reply-To: <B62A5C5C-A627-487D-A132-930873704E30@webedia-group.com>
References: <B62A5C5C-A627-487D-A132-930873704E30@webedia-group.com>
On 2020-06-29 14:58, Mai Peng wrote:
> 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 ?
You need to be more specific what exactly you are doing, including
specific commands. For example, "pointing to" is not a specific enough
technical term.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, maily.peng@webedia-group.com, yannick.le-guedart@webedia-group.com
Subject: Re: After renaming a database the subscription ( logical replication) stay sticky to the old database (master)
In-Reply-To: <cbfc0551-0339-2a16-05b1-9a52a4fa4e5c@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox