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

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Mai Peng <maily(dot)peng(at)webedia-group(dot)com>, pgsql-admin(at)postgresql(dot)org
Cc: Yannick Le Guédart <yannick(dot)le-guedart(at)webedia-group(dot)com>
Subject: Re: After renaming a database the subscription ( logical replication) stay sticky to the old database (master)
Date: 2020-06-29 17:10:12
Message-ID: cbfc0551-0339-2a16-05b1-9a52a4fa4e5c@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message srini ram 2020-06-29 17:18:28 pg_dump backup issue
Previous Message Scott Ribe 2020-06-29 16:58:57 Re: pg_basebackup compression