Hi Justin,
thanks for the heads up - can you create separate GitHub issues for
these things and everything else that should go into the patch release?
I just added another issue today. Will try to create a bugfix release
covering these things over the weekend then.
Yes, the frontend/backend-protocol doesn't matter for us since libpq
takes care of that.
-- Christoph
On 11.06.2021 16:43, Justin Pryzby wrote:
It looks like inserttable() fails to call endcopy() when it raises exceptions
after calling "copy from":
else {
PyErr_SetString(
PyExc_TypeError,
"The second argument must contain a tuple or a list");
return NULL;
}
This causes protocol errors:
$ python3.5 -c "import pg; d=pg.DB('dbname=postgres host=/tmp');
d.inserttable('loc2', ['b', 'c'])"
Traceback (most recent call last):
File "<string>", line 1, in <module>
TypeError: The second argument must contain a tuple or a list
...
2021-03-05 14:36:41.297 CST client backend[7161] [unknown] ERROR: unexpected
message type 0x58 during COPY from stdin
It looks like this was previously broken by 7f1e84d88, fixed (incidentally) by
b8bd9f763, and most recently broken by b8bd9f763.
Also, it looks like PQputline is deprecated.
Also, note that postgres v14 has removed protocol version 2 - I think we don't
have to care since we just link to lipq.
Also, is it possible to make a patchlevel release for the last few bugfixes ?
Cheers,
Justin
_______________________________________________
PyGreSQL mailing list
PyGreSQL@Vex.Net
https://mail.vex.net/mailman/listinfo/pygresql
