I said before I have tried in a single threaded test case with the same issue.
On Tue, Jul 17, 2018 at 9:39 AM, Christoph Zwerschke <c...@online.de> wrote: > Am 12.07.2018 um 00:59 schrieb M P: > >> I've used this in a single threaded program and it had this error. I >> swapped with another python pgsql driver and used the same exact queries >> without an issue. >> > > We'd be glad if you could provide a reproducible single threaded test case > for this issue if you really think this is a bug. To me it still looks like > a threading issue. > > Note that PyGreSQL has only threadsafety 1 (module level), while Psycopg2 > has threadsafety 2 (connection level) - they are using a global connection > lock. That would explain the difference in behavior. > > -- Christoph > > _______________________________________________ > PyGreSQL mailing list > PyGreSQL@vex.net > https://mail.vex.net/mailman/listinfo.cgi/pygresql >
_______________________________________________ PyGreSQL mailing list PyGreSQL@vex.net https://mail.vex.net/mailman/listinfo.cgi/pygresql
