(thread moved from pg_bugs)
(upgrading a 8.0.13 database on Windows XP 32bit to 9.5.1 on Windows 8
64 bit.....)
On 3/1/2016 8:05 PM, Premsun Choltanwanich wrote:
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):
pg_dump: reading rewrite rules
pg_dump: reading policies
pg_dump: reading large objects
...
pg_dump: creating FUNCTION "public.plpgsql_call_handler()"
pg_dump: creating FUNCTION "public.plpgsql_validator(oid)"
...
pg_dump: creating FUNCTION "public.pg_file_write(text, text, boolean)"
those all sound like standard postgres functions, its not clear to me
why pg_dump is generating the CREATE FUNCTION code for them.
pg_dump: [archiver] could not write to output file: Invalid argument
ok, presumably your new box has plenty of disk space? try this on the
new 9.5 system...
"C:\Program Files\PostgreSQL\9.5\bin\pg_dump" -v -h 192.168.200.75
-U clubadmin -d clubprogram -f "D:\Backups\clubprogram-2016-03-01.sql"
(replace D:\Backups\ with wherever you want to put this potentially
rather large backup file)
if that works, then ...
"C:\Program Files\PostgreSQL\9.5\bin\psql" -U clubadmin -d
clubprogram -f "D:\Backups\clubprogram-2016-03-01.sql"
should load the dumped data onto the new system.
--
john r pierce, recycling bits in santa cruz
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
