From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Blewett <david(at)dawninglight(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Add encoding support to COPY |
Date: | 2009-07-15 16:17:29 |
Message-ID: | 24121.1247674649@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Blewett <david(at)dawninglight(dot)net> writes:
> 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.
Well, it might make sense to allow an ENCODING option attached to a COPY
with a file source/destination. I remain of the opinion that overriding
client_encoding on a transfer to/from the client is a bad idea.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-07-15 16:23:08 | Re: [GENERAL] pg_migrator not setting values of sequences? |
Previous Message | Tom Lane | 2009-07-15 16:10:41 | Re: [GENERAL] pg_migrator not setting values of sequences? |