Re: raw output from copy
От | Pavel Golub |
---|---|
Тема | Re: raw output from copy |
Дата | |
Msg-id | CAEu9NuhbT76stU7gU-0vsZxfSeebUCPPcm+B4_2ueFgTKgTaBw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: raw output from copy (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: raw output from copy
|
Список | pgsql-hackers |
Hello Pavel.
I looked through the patch. Sources are OK. However I didn't find any docs and test cases. Would you please provide me with short description on this feature and why it is important. Because I didn't manage to find the old Andrew Dunstan's post either.
I looked through the patch. Sources are OK. However I didn't find any docs and test cases. Would you please provide me with short description on this feature and why it is important. Because I didn't manage to find the old Andrew Dunstan's post either.
On Sat, Apr 11, 2015 at 12:26 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
PavelRegardsHiI 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 ms2015-04-09 20:48 GMT+02:00 Pavel Stehule <pavel.stehule@gmail.com>:PavelRegardsObjections? Ideas?It requires only one row, one column result - and result is just raw binary data without size.I propose to implement new format option "RAW" like Tom proposed.HiThis thread was finished without real work. I have a real use case - export XML doc in non utf8 encoding.
http://www.postgresql.org/message-id/16174.1319228878@sss.pgh.pa.us
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
--
Nullus est in vitae sensus ipsa vera est sensus.
В списке pgsql-hackers по дате отправления: