Hi Rahul, You may look into the following blogs.
https://www.percona.com/blog/2019/04/12/fast-upgrade-of-legacy-postgresql-with-minimum-downtime-using-pg_upgrade/ https://www.percona.com/blog/2019/04/04/replication-between-postgresql-versions-using-logical-replication/ https://www.percona.com/blog/2019/04/09/continuous-replication-from-legacy-postgresql-version-using-slony/ https://www.percona.com/blog/2019/03/27/postgresql-upgrade-using-pg_dump-pg_restore/ https://www.percona.com/blog/2019/03/18/postgresql-upgrade-using-pg_dumpall/ https://www.percona.com/resources/webinars/upgrading-migrating-your-legacy-postgresql-newer-postgresql-versions Thanks, Avinash. On Wed, Jun 12, 2019 at 10:31 AM Andreas Kretschmer <andr...@a-kretschmer.de> wrote: > > > Am 12.06.19 um 14:50 schrieb Rahul Chordiya: > > postgres=# > > postgres=# select subscription_name, status FROM > > pglogical.show_subscription_status(); > > subscription_name | status > > -------------------+-------- > > (0 rows) > > > > postgres=# select pglogical.create_subscription(subscription_name := > > 'subscription1', provider_dsn := 'host=10.101.40.70 port=5432 > > dbname=registration user=repuser password=password', replication_sets > > := '{my_set}'); > > *ERROR: could not fetch remote node info: ERROR: schema "pglogical" > > does not exist* > > > > What should I do? > > > > you have create the replication set (on the provider) in the > postgres-database, but now you referencing to an other database, > registration. There isn't this replication set defined. > > > Regards, Andreas > > -- > 2ndQuadrant - The PostgreSQL Support Company. > www.2ndQuadrant.com > > > > -- 9000799060
