Re: pg_upgrade from 9.5 to 9.6 fails with "invalid argument"
От | Adrian Klaver |
---|---|
Тема | Re: pg_upgrade from 9.5 to 9.6 fails with "invalid argument" |
Дата | |
Msg-id | bb41f587-d7bb-3de6-6cf8-a0e0fb86607f@aklaver.com обсуждение исходный текст |
Ответ на | pg_upgrade from 9.5 to 9.6 fails with "invalid argument" (Thomas Kellerer <spam_eater@gmx.net>) |
Ответы |
Re: pg_upgrade from 9.5 to 9.6 fails with "invalid argument"
|
Список | pgsql-general |
On 09/29/2016 12:50 PM, Thomas Kellerer wrote: > Hello, > > for some reason pg_upgrade failed on Windows 10 for me, with an error > message that one specifc _vm file couldn't be copied. > > When I try to copy that file manually everything works fine. > > After running a "vacuum full" on the table in question the upgrade goes > through. Assuming you did that on old cluster? Upgrading to 9.6? Where both clusters installed the same way? > > One thing I noticed in the --verbose output of pg_upgrade is that the > old cluster - despite being a 9.5 one - has the "pg_control version > number 942" Which is correct: https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/include/catalog/pg_control.h;h=0b8bea74a891831bc3cbe8fd4d4233475a8329c4;hb=ba37ac217791dfdf2b327c4b75e7083b6b03a2f5 What was the complete command line invocation of pg_upgrade? > > Here is the part of the pg_upgrade output: > > ..... > > copying "d:/Daten/db/pgdata95/base/16410/85351" to > "d:/Daten/db/pgdata96/base/16411/85351" > d:/Daten/db/pgdata95/base/16410/85351_fsm > copying "d:/Daten/db/pgdata95/base/16410/85351_fsm" to > "d:/Daten/db/pgdata96/base/16411/85351_fsm" > d:/Daten/db/pgdata95/base/16410/85351_vm > copying "d:/Daten/db/pgdata95/base/16410/85351_vm" to > "d:/Daten/db/pgdata96/base/16411/85351_vm" > d:/Daten/db/pgdata95/base/16410/85358 > copying "d:/Daten/db/pgdata95/base/16410/85358" to > "d:/Daten/db/pgdata96/base/16411/85358" > d:/Daten/db/pgdata95/base/16410/85358.1 > copying "d:/Daten/db/pgdata95/base/16410/85358.1" to > "d:/Daten/db/pgdata96/base/16411/85358.1" > d:/Daten/db/pgdata95/base/16410/85358.2 > copying "d:/Daten/db/pgdata95/base/16410/85358.2" to > "d:/Daten/db/pgdata96/base/16411/85358.2" > d:/Daten/db/pgdata95/base/16410/85358.3 > copying "d:/Daten/db/pgdata95/base/16410/85358.3" to > "d:/Daten/db/pgdata96/base/16411/85358.3" > d:/Daten/db/pgdata95/base/16410/85358_fsm > copying "d:/Daten/db/pgdata95/base/16410/85358_fsm" to > "d:/Daten/db/pgdata96/base/16411/85358_fsm" > d:/Daten/db/pgdata95/base/16410/85358_vm > copying "d:/Daten/db/pgdata95/base/16410/85358_vm" to > "d:/Daten/db/pgdata96/base/16411/85358_vm" > > error while copying relation "public.wb_downloads" > ("d:/Daten/db/pgdata95/base/16410/85358_vm" to > "d:/Daten/db/pgdata96/base/16411/85358_vm"): Invalid argument > Failure, exiting > > The file in question is 65.536 bytes in size. > > I saved all log files and the complete output from the failed run, so if > you are interested I can supply them (I ran pg_upgrade with the --retain > option). > > Regards > Thomas > > > > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: