Re: raw output from copy

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: raw output from copy
Date: 2015-04-15 20:11:43
Message-ID: CAFj8pRD2BY-gkbUBsGF=WYb_tCVPTiBZe35VCoJX8EXF0Qh1Ng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

It would be nice, but it is not true. You can get correct non utf8 xml with
encoding specification only when binary mode is used. Psql doesn't support
binary mode.

Regards

Pavel
Dne 15. 4. 2015 22:06 napsal uživatel "Peter Eisentraut" <peter_e(at)gmx(dot)net>:

> On 4/10/15 5:26 PM, Pavel Stehule wrote:
> > Hi
> >
> > I wrote a prototype of this patch, and it works well
> >
> > postgres=# set client_encoding to 'latin2';
> > SET
> > Time: 1.488 ms
> > postgres=# \copy (select xmlelement(name xx, d) from d) to ~/d.xml
> > (format 'raw')
> > COPY 1
> > Time: 1.108 ms
> > postgres=# copy (select xmlelement(name xx, d) from d) to stdout (format
> > 'raw') ;
> > <?xml version="1.0" encoding="LATIN2"?><xx>příliš žluťoučký
> > kůň</xx>Time: 1.000 ms
>
> I think you can get the same thing using regular psql output and just
> turning off all field and record separators and tuple headers and so on.
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-04-15 20:35:36 show xl_prev in xlog.c errcontext
Previous Message Peter Eisentraut 2015-04-15 20:06:40 Re: raw output from copy