From: Daniel Henrique Alves Lima <email_daniel_h@yahoo.com.br>
To: pgsql-sql@postgresql.org
Subject: Re: About pg_dump
Date: Thu, 11 Mar 2004 18:13:18 -0300
Message-ID: <4050D66E.4050706@yahoo.com.br> (raw)
In-Reply-To: <20281.1079020997@sss.pgh.pa.us>
References: <404F9DFE.7000306@yahoo.com.br>
<016701c40779$bbf9bd00$97ed89c1@etur>
<20281.1079020997@sss.pgh.pa.us>
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@eselx.ipl.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
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: email_daniel_h@yahoo.com.br
Subject: Re: About pg_dump
In-Reply-To: <4050D66E.4050706@yahoo.com.br>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox