Open lpossamai opened 1 year ago
For people finding this issue - I would recommend triple-checking the "limitations and restrictions" part of the Readme and ensure that you do absolutely respect them. We have discovered after significant effort that the pglogical worker on the replica would just crash when it encounters some of these corner cases, leading to the aforementioned issue, with not much logging for troubleshooting.
In our case - we were using deferred index updates and did not immediately realize the incompatibility. It took quite a lot of effort to figure out this was the root cause of this error. Hope this is useful to people finding this issue :bow:
Hi there!
I'm setting up a brand new PGlogical connection between two PostgreSQL 14 versions.
The Source database is (AWS EC2 Instance): pglogical version on source:
2.4.2-2.pgdg20.04+1
postgres version on source:PostgreSQL 14.7 (Ubuntu 14.7-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
The Target database is (AWS RDS Aurora V2 with RDS Proxy): pglogical version on target:
2.4.1
postgres version on target:PostgreSQL 14.6 on aarch64-unknown-linux-gnu, compiled by aarch64-unknown-linux-gnu-gcc (GCC) 7.4.0, 64-bit
Once initial sync has been completed (+900GB), the subscriber is shown as
down
(select * from pglogical.show_subscription_status();
):Log from the target (RDS):
The query
SELECT * FROM pglogical.local_sync_status WHERE sync_status <> 'r';
returns no results.What else could I check, please?
Thanks in advance! Lucas