pglogical

pglogical copied to clipboard

ERROR: cannot copy from partitioned table

12

PG 13.2, Pglogical: 2.3.3 I have three servers: old_master **(A)** with non partitioned big table, new_master **(B)** with partitioned table ready to replicate data from A, and next replica with...

ZiBiS

Truncate CASCADE brings pglogical subscriber down

1

I have two source databases and one target database. I have setup pglogical replication between the two source dbs to the target db source db1 -> replicates few tables to...

sreejithvelath

Unable to replicate table with generated columns

5

read from bottom up: ``` 2021-08-19 08:30:08.503 UTC [31947]: [2-1] db=platform,user=logicalrepluser LOG: unexpected EOF on client connection with an open transaction -- 2021-08-19 08:30:08.502 UTC [31947]: [1-1] db=platform,user=logicalrepluser LOG: could...

danielkucera

Replication slot on provider disappears

6

I had a PG9 provider and a PG13 subscriber where the initial data sync was running (for 4days). I noticed `pglogical.show_subscription_status` on the subscriber transitioned to `down` and that the...

joshuabaird

Hi, When I try to run: select pglogical.alter_subscription_disable(name true) followed by: select pglogical.drop_subscription(name; while pglogical.show_subscription_status(); returns "initializing" status then drop command just stuck Is there any other way to gracefully...

rhollins

What is the prefered way of dealing with sequeneces replication

1

Hi, I'm trying to find the best way to deal with sequence replication: Currently, I'm adding all sequences this way when we setup replication: SELECT pglogical.replication_set_add_all_sequences(set_name := ssome_name, schema_names :=...

rhollins

Pglogical 2.1.1 CONFLICT: remote UPDATE on relation ... DETAIL: existing local tuple

10

i'm using version pglogical 2.1.1 to deploy the model 2 node postgres provider -> subscribe When the provider that runs 1 dml updates an existing row, subscribe appears as an...

flykent

Replication is in "initializing" status for a long time (looks like lack of documentation)

4

Hi! I set up replication for a big database (~1.7T) and it is in **initializing** state for a long time (~1 week) Database is in-use, I can't stop INSERTS/UPDATES/DELETES ```...

evgeniagusakova

I am having the same issue replicating a 2T database. the status of subscription remain as initializing. No errors in the logs SELECT * FROM pglogical.show_subscription_status();

mjuvette

segmentation fault on pglogical 2.4.1 with replication from non-partitioned to partitioned

3

I have a 9.6 database which is being upgraded to 13. We are using pglogical 2.4.1 as part of the process of migration. pglogical here is important to decrease down...

jcasanov