On 27/04/13 02:48, Tom Lane wrote:
Robert Haas writes:
On Thu, Apr 25, 2013 at 1:56 PM, Tom Lane wrote:
However, the documentation in libpq.sgml is a bit bogus too, because it
counsels trying the PQputCopyEnd() call again, which will not work
(since we already changed the asyncStatus). We co
On Fri, Apr 26, 2013 at 10:48 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Thu, Apr 25, 2013 at 1:56 PM, Tom Lane wrote:
>>> However, the documentation in libpq.sgml is a bit bogus too, because it
>>> counsels trying the PQputCopyEnd() call again, which will not work
>>> (since we already cha
Robert Haas writes:
> On Thu, Apr 25, 2013 at 1:56 PM, Tom Lane wrote:
>> However, the documentation in libpq.sgml is a bit bogus too, because it
>> counsels trying the PQputCopyEnd() call again, which will not work
>> (since we already changed the asyncStatus). We could make that say "a
>> zero
On Thu, Apr 25, 2013 at 1:56 PM, Tom Lane wrote:
> However, the documentation in libpq.sgml is a bit bogus too, because it
> counsels trying the PQputCopyEnd() call again, which will not work
> (since we already changed the asyncStatus). We could make that say "a
> zero result is informational, y
Robert Haas writes:
> Noah Misch pointed out something interesting to me:
> /*
> * PQputCopyEnd - send EOF indication to the backend during COPY IN
> *
> * After calling this, use PQgetResult() to check command completion status.
> *
> * Returns 1 if successful, 0 if data could not be sent (o
