Closed skel0 closed 3 months ago
Seems to be the same issue as: https://github.com/dimitri/pgcopydb/issues/700
Hi,
Just one comment. I already tried the workaround, which is to include the header partitioned tables in the [exclude-table-data] section, but still getting the error for some tables that are listed in the mentioned section. Don't know why pgcopydb is not skipping some of the tables mentioned in the [exclude-table-data] section (in my case 12 out of 68 are not excluded and still causing the errors).
Thanks.
Hi @skel0 ; please try again with a fresh build from the current sources, where I believe your issue might be fixed entirely thanks to today's merge. Also consider adding more information in this issue, allowing to re-open it if more work is needed. Thanks
Hi @dimitri,
I can confirm that now, using the latest commit, the clone process works like a charm :)
Thanks for your support!
Regards,
JL
Hi,
My scenario: Clone from PostgreSQL v15.2 running on CentOS 7.9 to Azure Database for PostgreSQL v16.2 Using pgcopydb 0.16.35.g30d7bcd from docker image.
I am getting errors almost at the end of the clone process for all partitioned tables. Seems that pgcopydb tries to do a truncate on the master table using "truncate only". The partitions have been copied. Just guess that pgcopydb tries to copy again the master tables and realizes that there is data (since the partitions have been copied earlier, seems that all are ok) and tries to truncate the master tables using "truncate only" which fails. All tables showing up in the errors are partitioned tables. The plain tables have been copied correctly.
This was reported also here:
Tried the workaround of adding the master tables in the [exclude-table-data] section of the filter file but didn't work (this workaround worked for me using pgcopydb 0.10 and I could sort this error out for this database with that version):
In the filter file I also configured to exclude some schemas...
...that part worked perfectly (indeed those show-up in the command line below):
Any suggestion to solve this?
Update: I am getting same error with other databases which are similar in terms of structure.
Thanks in advance!