Re: Recommended approach for upgrading DBs with nonmatching encodings - Mailing list pgsql-bugs

From Martin Pitt
Subject Re: Recommended approach for upgrading DBs with nonmatching encodings
Date
Msg-id 20080330203938.GO6486@piware.de
Whole thread Raw
In response to Recommended approach for upgrading DBs with nonmatching encodings  (Martin Pitt <martin@piware.de>)
Responses Re: Recommended approach for upgrading DBs with nonmatching encodings
List pgsql-bugs
Hi again,
Martin Pitt [2008-03-30 20:40 +0200]:
> My current pg_upgradecluster uses pg_dumpall to copy the schema, and a
> per-db pg_dump to copy the DB table contents. Will calling pg_dump
> with  --encoding=3D<encoding of 8.3 server's locale> always DTRT and is
> it meant to solve this problem?=20

One problem with this is that while pg_dump -E UTF8 works (with SQL
output), -E does not seem to have any effect when using -Fc. However,
-Fc is a must for a reasonably robust automatic upgrade script.

Thanks in advance,

Martin
--=20
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

pgsql-bugs by date:

Previous
From: Martin Pitt
Date:
Subject: Recommended approach for upgrading DBs with nonmatching encodings
Next
From: Tom Lane
Date:
Subject: Re: Recommended approach for upgrading DBs with nonmatching encodings