Skip to content
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 run the migration when filtering and using a dedicated process to hold the snapshot. #868

Open
dcupif opened this issue Aug 13, 2024 · 1 comment

Comments

@dcupif
Copy link

dcupif commented Aug 13, 2024

I'm trying to migrate a subset of tables using the filtering capabilities. This migration needs to be performed with logical replication so that we can minimize the downtime window. Also, since the amount of data to move is quite big (~1TB), we wanted to use a dedicated process to hold the snapshot so we could resume the migration in case anything goes wrong.

Here's what I've tried:

# Screen Session `snapshot`
pgcopydb snapshot --follow --slot-name migration

# Screen Session `migration`
pgcopydb clone --follow --slot-name migration --filters filter.ini ...

Trying to do so results in the clone command to fail complaining that the current filtering differs from the filtering used to initialize the catalog. However, there is no option on pgcopydb snapshot to provide the same filtering config file. Is this something known?


pgcopydb version: v0.17

@rimbi
Copy link
Contributor

rimbi commented Aug 29, 2024

Hi @dcupif , I could not reproduce the case. I can check it if you can provide a script to reproduce it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants