From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Verite <daniel(at)manitou-mail(dot)org>, hlinnaka <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pavel Golub <pavel(at)microolap(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: raw output from copy |
Date: | 2016-03-31 06:40:02 |
Message-ID: | CAFj8pRASwdksT=wTOOa2PRVy4Ti=L7c4ZPAfOLHnK2SXccy-AQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2016-03-31 8:34 GMT+02:00 Craig Ringer <craig(at)2ndquadrant(dot)com>:
> On 30 March 2016 at 00:19, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> > I tested COPY RAW on old psql clients - and it is working without any
>> > problem - so when the client uses same logic as psql, then it should to
>> > work. Sure, there can be differently implemented clients, but the COPY
>> > client side is usually simple - store stream to output.
>>
>> My point is precisely that I doubt all clients are that stupid about COPY.
>>
>
> PgJDBC definitely isn't.
>
> Any changes really need to be tested against PgJDBC's CopyManager.
>
this patch doesn't break any old application. Accepting new feature depends
on binary method detection. PQbinaryTuples based clients should to support
COPY RAW* without problems, PQfformat() should to report unknown format.
Regards
Pavel
>
>
> --
> Craig Ringer http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2016-03-31 06:42:50 | Re: PATCH: index-only scans with partial indexes |
Previous Message | Craig Ringer | 2016-03-31 06:34:51 | Re: raw output from copy |