| From: | Daniel Henrique Alves Lima <email_daniel_h(at)yahoo(dot)com(dot)br> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: About pg_dump |
| Date: | 2004-03-11 21:13:18 |
| Message-ID: | 4050D66E.4050706@yahoo.com.br |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
I've made a test and it seems ok to me. I'm using utf-8 encoding
under postgresql 7.3.3.
Tom Lane wrote:
>"Rute Solipa" <rutes(at)eselx(dot)ipl(dot)pt> writes:
>
>
>>it seems that the pg_dump command doesn't keep the encoding information.
>>
>>
>
>As of 7.4.2 it does emit a SET client_encoding.
>
>In prior releases, if you are manually creating the destination database
>then you need to be careful to create it with the same encoding as before.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Louie Kwan | 2004-03-11 21:17:27 | IMPORT TOOL |
| Previous Message | Jonathan Gardner | 2004-03-11 20:14:45 | Re: Break a report in Run Time |