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.
On Wed, Jul 11, 2018, 13:37 Justin Pryzby <[email protected]> wrote: > On Wed, Jul 11, 2018 at 08:14:45PM +0200, Christoph Zwerschke wrote: > > Am 29.06.2018 um 22:40 schrieb M P: > > > I may have found a bug in the driver. See the SO post here: > > > > > > > https://stackoverflow.com/questions/51108552/pygresql-insufficient-data-in-t-message > > > > See my reply on SO. I don't think it has anything to do with PyGreSQL, > and > > without a reproducible test case it's hard to say what's going on. > > Could also be due to forking subprocesses inherited an FD to same DB > session > and writing simultaneously. > The same applies to pygres as applies to psycopg: > > http://initd.org/psycopg/docs/usage.html#thread-safety > |libpq connections shouldn’t be used by a forked processes, so when using a > |module such as multiprocessing or a forking web deploy method such as > FastCGI > |make sure to create the connections after the fork. > > Justin > _______________________________________________ > PyGreSQL mailing list > [email protected] > https://mail.vex.net/mailman/listinfo.cgi/pygresql >
_______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo.cgi/pygresql
