Subject: Re: After renaming a database the subscription ( logical replication)
 stay sticky to the old database (master)
To: Mai Peng <maily.peng@webedia-group.com>, pgsql-admin@postgresql.org
References: <B62A5C5C-A627-487D-A132-930873704E30@webedia-group.com>
Cc: =?UTF-8?Q?Yannick_Le_Gu=c3=a9dart?= <yannick.le-guedart@webedia-group.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <cbfc0551-0339-2a16-05b1-9a52a4fa4e5c@2ndquadrant.com>
Date: Mon, 29 Jun 2020 19:10:12 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0)
 Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <B62A5C5C-A627-487D-A132-930873704E30@webedia-group.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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