Greg Sabino Mullane wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
The saga continues. I've reverted to a multi-step process to try and
figure this out. I create the initial database, then load it from the
command line psql as follows:
pro-# \set session_replication_role replica;
pro-# \o db.out
pro-# \i dump.txt
This is a database set, not a psql on, so you do not want the
backslash before the "set".
SET session_replication_role = replica;
I'd recommend adding a:
SHOW session_replication_role;
to the dump.txt as a sanity check.
For the sake of completeness, I've attempted the above, same result. We
have decided to take a different approach and attempt to clean up the
data in the database, then convert.
I do appreciate all the time you've devoted to this. There must be
something in the dump that is causing these issues.
Thanks again Greg. I'll certainly update the list once we have a
working solution.
- --
Greg Sabino Mullane greg@xxxxxxxxxxxx
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201102211529
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAk1iy74ACgkQvJuQZxSWSsgWQACgrxKDvN/yCZD5GZJvlqFMyyIC
9mwAnjOMJ9QDRa3IoiBCvaS9mT5sMR6f
=JYCs
-----END PGP SIGNATURE-----
--
Until later, Geoffrey
"I predict future happiness for America if they can prevent
the government from wasting the labors of the people under
the pretense of taking care of them."
- Thomas Jefferson
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
