Add pg_dump --encoding.
Patch applied. Thanks.
---
Magnus Hagander wrote:
> > > I *think* that's easy enough to do in time for 8.1. Trivial patch
> > > attached. I hope it's enough :-) It passed my very quick testing...
Alvaro Herrera wrote:
On Tue, Jun 28, 2005 at 10:24:19PM +0200, Magnus Hagander wrote:
I *think* that's easy enough to do in time for 8.1. Trivial patch
attached. I hope it's enough :-) It passed my very quick testing...
(Yup, I read the mails aobut PGCLIENTENCODING, but an option to pg_dump
> >> I *think* that's easy enough to do in time for 8.1. Trivial patch
> >> attached. I hope it's enough :-) It passed my very quick testing...
> >>
> >> (Yup, I read the mails aobut PGCLIENTENCODING, but an option to
> >> pg_dump is certainly easier)
> >
> > You forgot to document the long optio
> > I *think* that's easy enough to do in time for 8.1. Trivial patch
> > attached. I hope it's enough :-) It passed my very quick testing...
> >
> > (Yup, I read the mails aobut PGCLIENTENCODING, but an option to
> > pg_dump is certainly easier)
>
> You forgot to document the long option, I th
On Tue, Jun 28, 2005 at 10:24:19PM +0200, Magnus Hagander wrote:
> I *think* that's easy enough to do in time for 8.1. Trivial patch
> attached. I hope it's enough :-) It passed my very quick testing...
>
> (Yup, I read the mails aobut PGCLIENTENCODING, but an option to pg_dump
> is certainly eas
> 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