Open arajkumar opened 7 months ago
Hi @arajkumar ; that's a good idea for a needed feature. Do you want to work on it?
@dimitri , Absolutely! I already have a WIP patch, will create a PR soon. Thanks for reviewing this issue.
@arajkumar Did you get any further with this?
@theothornhill We have implemented on our fork which is yet to be upstreamed. The implementation also has to adopt the new sqlite catalog changes, hopefully will do some overhaul next week.
Good news! I'm available to test, if needed :)
Hey @arajkumar!
Would your PR be pushed anytime soon? I have an exact use case for this feature 🥹 I'd be happy to contribute incase you need an extra pair of helping hands or typing fingers? 🤔
Hello @jarvis-telus, Sorry, I don't have time to work on this atm.
I can share the work which I did on our fork, feel free to take it forward.
https://github.com/arajkumar/pgcopydb/commit/d3297962bf199e5959f94c04015fa35835718516
As far as the extension migration is concerned, pgcopydb supports either all or nothing approach via
--skip-extensions
CLI flag.While it might work for most use cases, it does not work in a few instances where the source includes extensions that are not directly consumed by the application but are provided only for management purposes by some cloud providers. e.g. https://github.com/aiven/aiven-extras
When attempt migration from the source which has extensions like above, pgcopydb would fail because the same extension won't be available in the target as it is not really needed.
It is not possible to drop those extension on source due to restrictions. I think the only option would be discarding them during migration using filters.
My proposal is to introduce a new filtering section, [exclude-extension] and take list of extension to be excluded during migration.
filter.ini