From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | David Blewett <david(at)dawninglight(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Add encoding support to COPY |
Date: | 2009-07-15 18:20:16 |
Message-ID: | 20090715182016.GM4551@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Blewett wrote:
> 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 could see a use case for remote client code to do a COPY to STDOUT,
> that is actually being redirected to a file. If the consensus is for
> local file-based operations only, however, I can structure the patch
> that way.
Yeah, the problem is that reading to/from files is only allowed to
superusers ...
(I'm not sure how this affects \copy in psql; probably something you
should investigate)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Wilson | 2009-07-15 18:25:27 | changing enumlabel from a NameData to text |
Previous Message | Bernd Helmle | 2009-07-15 18:05:28 | Re: Add encoding support to COPY |