Drop and re-create indices for faster catchup on large databases about pg_easy_replicate HOT 5 CLOSED

I got this written in my article about using logical replication to upgrade PSQL
https://dev.to/pikachuexe/postgresql-logical-replication-for-upgrade-41hl - Failed Attempts #2

from pg_easy_replicate.

Closed via #81

Can't start_sync, because it tries to drop indices in wrong order:
Starting sync failed: PG::DependentObjectsStillExist: ERROR: cannot drop index auth_tokens_auth_attempt_id_key because constraint auth_tokens_auth_attempt_id_key on table auth_tokens requires it
HINT: You can drop constraint auth_tokens_auth_attempt_id_key on table auth_tokens instead.

from pg_easy_replicate.

Closed via #81

from pg_easy_replicate.

ah! i see. thanks for the report. Is that the foreign key constraint?

UPDATE: Ah! its likely a unique constraint or primary key

from pg_easy_replicate.

0.2.1 is out with the fix https://github.com/shayonj/pg_easy_replicate/releases/tag/v0.2.1

thanks again for the report. let me know if you run into any issues.

from pg_easy_replicate.