Re: PQputCopyEnd doesn't adhere to its API contract - Mailing list pgsql-hackers

From Robert Haas
Subject Re: PQputCopyEnd doesn't adhere to its API contract
Date
Msg-id CA+TgmoYZiZ+pf6yCHMVt2X2nXotLCQnrpVd5XG4S4CRnwDny6g@mail.gmail.com
Whole thread Raw
In response to Re: PQputCopyEnd doesn't adhere to its API contract  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PQputCopyEnd doesn't adhere to its API contract
List pgsql-hackers
On Thu, May 8, 2014 at 1:51 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> OK.  It still seems to me that there's a doc fix needed here, if
>> nothing else.  The documentation for PQputCopyEnd() clearly implies
>> that if you get a return value of 1, the message is sent, and that's
>> just not true.
>
> That's fair.

Something like the attached?

I don't really know what to say about 0, since it's never actually
returned, so I left that out.  But I'm up for suggestions.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Sending out a request for more buildfarm animals?
Next
From: Stephen Frost
Date:
Subject: Re: [v9.5] Custom Plan API