Re: Re: could not migrate 8.0.13 database with large object data to 9.5.1

On 02/03/16 18:21, Mark Kirkwood wrote:
> On 02/03/16 17:05, Premsun Choltanwanich wrote:
>> Hi John,
>>
>> Modified command by remove -Ft flag as per you suggestion:
>> pg_dump -v -h 192.168.200.75 -U clubadmin -d clubprogram | psql -U
>> clubadmin -d clubprogram
>>
>> Result (got same message even with parameter -b or not):
>
> (snippage)
>
>> pg_dump: creating FUNCTION "public.pg_database_size(oid)"
>> pg_dump: creating FUNCTION "public.pg_dir_ls(text, boolean)"
>> pg_dump: creating FUNCTION "public.pg_file_length(text)"
>> pg_dump: creating FUNCTION "public.pg_file_read(text, bigint, bigint)"
>> pg_dump: creating FUNCTION "public.pg_file_rename(text, text)"
>> pg_dump: creating FUNCTION "public.pg_file_rename(text, text, text)"
>> pg_dump: creating FUNCTION "public.pg_file_stat(text)"
>> pg_dump: creating FUNCTION "public.pg_file_unlink(text)"
>> pg_dump: creating FUNCTION "public.pg_file_write(text, text, boolean)"
>> pg_dump: [archiver] could not write to output file: Invalid argument
>>
>> Please advise.
>>
>
> I'd guess you are running into something like
>
> http://stackoverflow.com/questions/15672651/failure-using-heroku-pgtransfer
>
> i.e old functions that cannot be recreated in 9,5, maybe check the logs
> on the 9.5 server for the reason you are seeing 'invalid argument'.
>
> You may need to drop those pg_file_* and pg_database_size functions
> (they are not native to 8.0...I checked...had to compile a 8.0.26, which
> was interesting).
>

I tested that idea out (adding in the dbsize contrib for 8.0 and doing
dump/restore to 9.5) and while I see errors for *those* functions,
everything else (i.e tables etc) are loaded into 9.5 ok.

So something else is tripping you up - have a look at the postgres logs
for the 8.0 and 9.5 systems.

Cheers

Mark