ot;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
reSQL 9.5 or
later.
In 9.4 or before, you need to take whole backup from the new master
server, for example using pg_basebackup.
Regards,
--
Masahiko Sawada
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
pplication_name=node1'+
(1 row)
You can get the master server information via SQL from standby server.
Regards,
--
Masahiko Sawada
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
o upgrading, I will suggest to take backup(pg_dumpall) from
current cluster and then restore it to new cluster.
I think pg_upgrade is basically used at major version upgrading.
Regards,
--
Masahiko Sawada
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general