Postgres Pro
Downloads
Home   >   mailing lists

Re: raw output from copy - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: raw output from copy
Date
Msg-id CAFj8pRBr3Z32wDb-p1ndS3sNKuMsffc=ftxUzZqxW-n6EbE6eg@mail.gmail.com
Whole thread Raw
In response to Re: raw output from copy  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: raw output from copy  (Robert Haas <robertmhaas@gmail.com>)
Re: raw output from copy  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Tree view
Hi

here is cleaned/finished previous implementation of RAW_TEXT/RAW_BINARY formats for COPY statements.

The RAW with text formats means unescaped data, but with correct encoding - input/output is realised with input/output function. RAW binary means content produced/received by sending/received functions.

Now both directions (input/output) working well

Some examples of expected usage:

copy (select xmlelement(name foo, 'hello')) to stdout (format raw_binary, encoding 'latin2');

create table avatars(id serial, picture bytea);
\copy avatars(picture) from ~/images/foo.jpg (format raw_binary);
select lastval();

create table doc(id serial, txt text);
\copy doc(txt) from ~/files/aaa.txt (format raw_text, encoding 'latin2');
select lastval();

Regards

Pavel

Attachment

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Typo in src/interfaces/libpq/fe-connect.c
Next
From: Fujii Masao
Date:
Subject: Re: Support for N synchronous standby servers - take 2