From: | David Blewett <david(at)dawninglight(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Add encoding support to COPY |
Date: | 2009-07-15 16:08:32 |
Message-ID: | 9d1f8d830907150908je524b9ey9a5cb7b40650025d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 15, 2009 at 12:04 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> What is the point? You'd generally have client_encoding set correctly
> for your usage anyway, and if you did not, the data could confuse your
> client-side code terribly. Offering an option to let the backend send
> data in the "wrong" encoding does NOT seem like a good idea to me.
The use case was that the client connection was using one encoding,
but needed to output the file in a different encoding. So they would
have to do the "set client_encoding" dance each time they wanted to
export the file. I don't see how it's "wrong", especially considering
there is already a method to do this, albeit cumbersome. I consider it
simply syntactic sugar over existing functionality.
David Blewett
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-07-15 16:10:41 | Re: [GENERAL] pg_migrator not setting values of sequences? |
Previous Message | Zdenek Kotala | 2009-07-15 16:04:29 | Re: [GENERAL] pg_migrator not setting values of sequences? |