| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] pg_upgrade from 9.5 to 9.6 fails with "invalid argument" |
| Date: | 2016-09-30 16:47:17 |
| Message-ID: | nsm4vt$afg$1@blaine.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Masahiko Sawada schrieb am 30.09.2016 um 12:54:
>> I did this on two different computers, one with Windows 10 the other with Windows 7.
>> (only test-databases, so no real issue anyway)
>>
>> In both cases running a "vacuum full" for the table in question fixed the problem and pg_upgrade finished without problems.
>
> Because vacuum full removes the _vm file, pg_upgrade completed job successfully.
> If you still have the _vm file
> ("d:/Daten/db/pgdata95/base/16410/85358_vm") that lead an error, is it
> possible that you check if there is '\r\n' [0d 0a] character in that
> _vm file or share that _vm file with us?
Yes, I saved one of the clusters.
The file can be downloaded from here: http://www.kellerer.eu/85358_vm
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-09-30 16:47:35 | Re: Parallel query only when EXPLAIN ANALYZEd |
| Previous Message | Tom Lane | 2016-09-30 16:38:51 | Re: [GENERAL] pg_upgrade from 9.5 to 9.6 fails with "invalid argument" |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2016-09-30 16:48:24 | Re: [GENERAL] pg_upgrade from 9.5 to 9.6 fails with "invalid argument" |
| Previous Message | Konstantin Knizhnik | 2016-09-30 16:40:05 | Re: On conflict update & hint bits |