I support to add the option, for I've been seeing too many of
our client got 'bad' dump just because they don't set PGCLIENTENCODING
correctly, (mostly because they use UTF8 as database encoding
but use some other encoding, like GBK as client encoding, but some
words break the autoconversion at pr
> There's no time to do this for 8.1, but I'd like to get it on
> the books for
> 8.2:
>
> The Problem: Occassionally a DBA needs to dump a database to a new
> encoding. In instances where the current encoding, (or lack of an
> encoding, like SQL_ASCII) is poorly supported on the target
> d
Josh Berkus wrote:
> currently the only way to set the encoding of a pg_dump file is to
> change client_encoding in postgresql.conf and restart postmaster.
Another way is to set the environment variable PGCLIENTENCODING.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---
On Tue, 28 Jun 2005, Josh Berkus wrote:
> The TODO: add an --encoding=[encoding name] option to pg_dump. This would
> set client_encoding for pg_dump's session(s).
>
What about just using the PGCLIENTENCODING environment variable?
Kris Jurka
---(end of broadcast)--
