pglogical

How can I get past this problem recreating a pg_logical subscription?

你。 提交于 2021-02-11 12:47:12
问题 I'm having a problem dropping and creating subscriptions - I think these messages are saying it exists on the replica and not the primary: db=# CREATE SUBSCRIPTION sub db-# CONNECTION 'dbname=db host=some.domain.com user=logical_replicator password=xxxxxxx' db-# PUBLICATION pub; ERROR: subscription "sub" already exists db=# DROP subscription sub; ERROR: could not drop the replication slot "sub" on publisher DETAIL: The error was: ERROR: replication slot "sub" does not exist How can I get this

How can I get past this problem recreating a pg_logical subscription?

跟風遠走 提交于 2021-02-11 12:45:53
问题 I'm having a problem dropping and creating subscriptions - I think these messages are saying it exists on the replica and not the primary: db=# CREATE SUBSCRIPTION sub db-# CONNECTION 'dbname=db host=some.domain.com user=logical_replicator password=xxxxxxx' db-# PUBLICATION pub; ERROR: subscription "sub" already exists db=# DROP subscription sub; ERROR: could not drop the replication slot "sub" on publisher DETAIL: The error was: ERROR: replication slot "sub" does not exist How can I get this

Notify from trigger on pglogical replicated table

萝らか妹 提交于 2019-12-11 06:08:06
问题 I'm trying to setup a push-from-server functionality based on PostgreSQL, pglogical and PostgreSQL's listen-notify mechanism. On my replicated table I've setup a trigger that uses pg_notify to push messages to queue after insert. Altered the trigger to "enable always trigger". With this setup, the behavior is not what I expected. After setting up a listen client (another postgresql console, also tried multiple python drivers, behavior is always the same), I don't get the notifications until I