Re: raw output from copy

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(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:48:56
Message-ID: CAMsr+YFPNSZ6sLBZBz0=Ng46HE4gqBw5L+ECfkizMjjicarXNg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-03-31 07:50:59 Re: [PATCH v1] GSSAPI encryption support
Previous Message Masahiko Sawada 2016-03-31 07:48:26 Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.