diff options
| author | Bruce Momjian <bruce@momjian.us> | 2005-07-10 15:08:52 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2005-07-10 15:08:52 +0000 |
| commit | d1cffe2f779d95ddb9f0607f284e2c6c3a71d566 (patch) | |
| tree | fccb89ecfc26c1ccbc87a6017a823d38e9abc834 /src/backend/regex/regcomp.c | |
| parent | 07931080360021376af8128b0ca297406a9ab121 (diff) | |
| download | postgresql-d1cffe2f779d95ddb9f0607f284e2c6c3a71d566.tar.gz postgresql-d1cffe2f779d95ddb9f0607f284e2c6c3a71d566.zip | |
Add --encoding to pg_dump.
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 database
server, it can be useful to dump into a particular encoding. But,
currently the only way to set the encoding of a pg_dump file is to
change client_encoding in postgresql.conf and restart postmaster.
This is more than a little awkward for production systems.
Magnus Hagander
Diffstat (limited to 'src/backend/regex/regcomp.c')
0 files changed, 0 insertions, 0 deletions