2011/10/21 Tom Lane <t...@sss.pgh.pa.us>:
> Pavel Stehule <pavel.steh...@gmail.com> writes:
>> 2011/10/21 Andrew Dunstan <andrew.duns...@pgexperts.com>:
>>> On 10/21/2011 02:44 PM, Pavel Stehule wrote:
>>>> isn't better to fix current tools to work well with bytea?
>>> Such as?
>> some like
>> \copy ... to foo.bin format binary
> No, because COPY BINARY will emit its own sort of wrappers around the
> data.

true - it's not useful for this case

> What I don't like about Andrew's proposal is that it seems rather
> limited.  Why bytea in particular?  Text chunks could probably also use
> a direct output method.  And what about input?
> Could we do anything with a notion of a COPY RAW mode, that would dump
> or read the data without any header, column, or row separators?  On
> input I suppose you'd have to restrict it to one column --- on output,
> we could leave re-dividing the data to the user's ingenuity ...


Andrew - has sense a  input/output different than 1row/1column?



>                        regards, tom lane

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to