pglogical cross subscribe

From: Andy Colson <andy(at)squeakycode(dot)net>
To: PostgreSQL general <pgsql-general(at)postgresql(dot)org>
Subject: pglogical cross subscribe
Date: 2016-08-04 01:27:38
Message-ID: eaadd7b0-5607-d8b0-cbc9-1492c415635c@squeakycode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all.

I have a localdb and a remotedb.

A) I'd like to send table1 and table2 from localdb to remotedb.
B) I'd like to send table3 from remotedb to localdb.

I have PG9.5 and pglogical setup, and (A) works fine.

Well, worked. I then tried to set up (B) which seems to work, but now (A) is broken.

remotedb is logging things like:
2016-08-03 20:20:17.086 CDT,: ERROR: cache lookup failed for replication origin 'pgl_vcstimes_katniss_subscrib73496c2'
2016-08-03 20:20:17.087 CDT,: LOG: worker process: pglogical apply 23704565:3237263450 (PID 21981) exited with exit code 1

I did find:
https://www.postgresql.org/message-id/1691408856.31522.1468333259045.JavaMail.zimbra@cobra.ru
which leads to this:
https://github.com/2ndQuadrant/pglogical/issues/23

But I'm not sure if that helps me, or if it does I don't understand what I'd need to do.

On remotedb, I see:
vcstimes=# select * from pglogical.show_subscription_status();
-[ RECORD 1 ]-----+-------------------------------------------------------
subscription_name | subscribe_katniss
status | down
provider_node | payroll_provider
provider_dsn | host=localhost port=9090 dbname=vcstimes user=postgres
slot_name | pgl_vcstimes_payroll_provider_subscribc0f4b85
replication_sets | {default,default_insert_only,ddl_sql}
forward_origins | {all}

I cannot find any description of status = down, and I don't know how to bring it back up. Any help would be appreciated.

Thanks,

-Andy

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Patrick B 2016-08-04 02:21:21 Question about wal files / pg_xlogs
Previous Message John R Pierce 2016-08-03 23:40:56 Re: connection file descriptors created with identical number after process fork on mac