Re: raw output from copy

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 07:54:34
Message-ID: CAFj8pRCy7HX0u=VVnusTSMNO4EexNKSgbBfnAMSH0eyFe3uEPg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2016-03-31 9:48 GMT+02:00 Craig Ringer <craig(at)2ndquadrant(dot)com>:

> On 31 March 2016 at 14:40, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
>
>> 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.
>>
>>
> PgJDBC does not use libpq.
>

so it can be interesting test

Pavel

>
> --
> Craig Ringer http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2016-03-31 08:01:25 Re: Relation extension scalability
Previous Message Andres Freund 2016-03-31 07:51:01 Re: Performance degradation in commit 6150a1b0