Re: Add encoding support to COPY

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 20:07:09
Message-ID: 1774.1247688429@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:17 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.

> I really don't see how it is any different from manually flipping the
> client_encoding before/after the transfer.

The difference is that the client-side code gets told that the encoding
changed if you do the latter.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Blewett 2009-07-15 20:19:55 Re: Add encoding support to COPY
Previous Message Dimitri Fontaine 2009-07-15 19:52:58 Re: more than one index in a single heap pass?