| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Proposed TODO: --encoding option for pg_dump |
| Date: | 2005-06-28 19:10:22 |
| Message-ID: | 200506281210.22856.josh@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Folks,
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 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.
The TODO: add an --encoding=[encoding name] option to pg_dump. This would
set client_encoding for pg_dump's session(s).
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2005-06-28 19:21:24 | Re: contrib/rtree_gist into core system? |
| Previous Message | Tom Lane | 2005-06-28 19:07:39 | Re: [PATCHES] Users/Groups -> Roles |