-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't drop extension after failed initial sync? #422
Comments
Found that there are MANY rows in pg_depend that relate to pglogical extension:
All dependencied with pg_class classid were to tables in pglogical schema. pg_proc - relates to pglogical.* functions. But the pg_trigger is weird. There point to triggers that I don't see in
pg_dump -s also doesn't show these triggers?! |
OK. So, after some thinking, I did:
and then drop extension pglogical;, and it seems to work fine. Perhaps it could be added to pglogical to remove obsolete triggers? Or maybe I missed mention in docs about it? |
Hi,
I was trying to setup pglogical replication from pg12 to pg14 of dataset with ~ 3tb.
after two days, we gave up. dropped all stuff related to pglogical form the pg14 side, and removed everything from pg12:
Which worked up to the drop extension.
Drop extension breaks, as it deadlocks with anything.
Checked all tables in pglogical schema, there were some rows in .queue table, and only this table, so i truncated this table.
But still can't drop the extension, it deadlocks with anything running on the system, and the deadlock message seems to point to one of the most commonly used tables.
Why does it deadlock? Can I do anything about it? There are no repsets, no repset tables, no nodes, nothing in any pglogical.* table.
The text was updated successfully, but these errors were encountered: