From: | momjian(at)svr1(dot)postgresql(dot)org (Bruce Momjian) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Add --encoding to pg_dump. |
Date: | 2005-07-10 15:08:53 |
Message-ID: | 20050710150853.319A352ACA@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
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
Modified Files:
--------------
pgsql/doc/src/sgml/ref:
pg_dump.sgml (r1.78 -> r1.79)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_dump.sgml.diff?r1=1.78&r2=1.79)
pgsql/src/bin/pg_dump:
pg_dump.c (r1.414 -> r1.415)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c.diff?r1=1.414&r2=1.415)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-07-10 15:19:43 | pgsql: The attached patch implements spi_query() and spi_fetchrow() |
Previous Message | Bruce Momjian | 2005-07-10 14:26:30 | pgsql: This patch implements putting language handlers for the optional |