--yVhtmJPUSI46BTXb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, May 13, 2008 at 09:00:49AM +0200, J. Manuel Velasco - UBILIBET
wrot=
e:
> Hello,
>=20
> I have installed a new postgresql server and I need to recover an old=20
> database on it.
> The database I have to recover has LATIN2 as encoding and when i try to=
=20
> restore it into the new one I get error messages due to encoding.
> I have read that from pgsql8-3 is not possible to have different=20
> encoding and since by default the encoding for postgres is UTF8 my
doubt=
=20
> is how can I restore the old database with no errors.
The encoding must match the collation, that's all. You don't say what
you are recovering, but pg_dump emits a "SET client_encoding=3Dlatin2",
right? In which case it should just work.
If it's something else you need to show us exactly what the error
message is.
If you want everything connecting to the database to think it's latin2,
do:
ALTER DATABASE foo SET client_encoding=3Dlatin2;
Have a nice day,
--=20
Martijn van Oosterhout <kleptog@[EMAIL PROTECTED]
> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while=20
> boarding. Thank you for flying nlogn airlines.
--yVhtmJPUSI46BTXb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIKUypIB7bNG8LQkwRAhbXAJsF9bChKb55Yt5Jd+CtAeyG/xFHdACeJhZs
CImCTRkqTShETLbDS5chVew=
=YDag
-----END PGP SIGNATURE-----
--yVhtmJPUSI46BTXb--
|
