Open djpenka opened 4 weeks ago
I manually performed the ALTER TABLE ... ADD CONSTRAINT ... USING INDEX
steps and now the pgcopydb compare schema
commands show no differences
I was able to see this happening live, and can confirm that there is a segmentation fault that occurs with the pgcopydb list progress --json
command while the database locking issues are occurring in the pgcopydb copy indexes --index-jobs
process
As part of the workaround for #876, I have been manually performing the pgcopydb steps for database migrations with the following steps:
During the
pgcopydb copy indexes
step, I ran into an issue where the sqlite database became locked, see logsThis was when I was mostly done creating about 1000 indexes. I got a stream of errors that new processes could not be created, and two current processes were unable to be deleted from the
process
table. They still show up inpgcopydb list progress --json
output. I tried to resume the index creation withpgcopydb copy indexes --resume
which completed successfully, along withpgcopydb copy constraints
. However, the next steppgcopydb restore post-data --no-owner --no-acl
ran into the following errorsAdditionally, output from
pgcopydb compare schema
gives the followingMy initial idea is to manually modify the destination table constraints to match the source, based on the output.