| From: | "Michael Paesold" <mpaesold(at)gmx(dot)at> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)surnet(dot)cl>, "Magnus Hagander" <mha(at)sollentuna(dot)net> |
| Cc: | <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Proposed TODO: --encoding option for pg_dump |
| Date: | 2005-06-28 20:48:56 |
| Message-ID: | 012801c57c22$cdcfff20$0f01a8c0@zaphod |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
>> is certainly easier)
>
> You forgot to document the long option, I think.
Are the man pages generated from the sgml docs? Have never had a look at
that.
Best Regards,
Michael Paesold
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2005-06-28 20:51:39 | Re: [HACKERS] Proposed TODO: --encoding option for pg_dump |
| Previous Message | Magnus Hagander | 2005-06-28 20:43:17 | Re: [HACKERS] Proposed TODO: --encoding option for pg_dump |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2005-06-28 20:51:39 | Re: [HACKERS] Proposed TODO: --encoding option for pg_dump |
| Previous Message | Magnus Hagander | 2005-06-28 20:43:17 | Re: [HACKERS] Proposed TODO: --encoding option for pg_dump |