Closed plvnv closed 2 months ago
+1 - Similar Issue
+1
Thanks for reporting the issue and confirming it; will have a look as soon as possible. If someone wants to see about fixing the issue in a Pull Request, please consider doing so, I will spend the necessary time to review and help get to a merge.
Quick look on our end points that the issue can be around these lines https://github.com/dimitri/pgcopydb/blob/v0.14/src/bin/pgcopydb/pgcmd.c/#L423-L447
Hey friends,
This one may help with fixing clone: https://github.com/dimitri/pgcopydb/pull/717
This one may help with fixing copy extensions if we can work out the schemas thing: https://github.com/dimitri/pgcopydb/pull/711
Review & input welcome.
ken.
I have these ready for review. Fix for clone
: https://github.com/dimitri/pgcopydb/pull/717 and fix for copy extensions
: https://github.com/dimitri/pgcopydb/pull/711.
@plvnv we've shipped the fix for pgcopydb clone
as described here: https://github.com/dimitri/pgcopydb/pull/717 if you build pgcopydb from main or wait for the 0.16 package, this should work better now.
good news thanks, I'll check it soon and give you feedback
Closing this issue for triage. The fix is already available in source code and building from source is covered in the docs.
pgcopy version
Running pgcopydb version 0.15.30.gcb55ea1
source db
PostgresPro (standard) 11.22.1
target dbPostgresPro (standard) 13.13.1
Can't clone extensions and objects using this extensions installed in non default schema
On source database extensions install in separate schema "extensions"
clone command
pgcopydb clone --follow --restart --table-jobs 4 --index-jobs 4 --plugin wal2json --wal2json-numeric-as-string
Error log