Use lo_creat() when possible instead of lo_create()
Reported by giomasce | January 9th, 2012 @ 10:34 PM
I'm using psycopg2 against a PostgreSQL database replicated using pgpool-II. On this database I also need large objects support. Apparently pgpool-II is able to correctly handle lo_creat() calls, but not lo_create() (see http://pgpool.projects.postgresql.org/pgpool-II/doc/pgpool-en.html#... ).
Unfortunately, psycopg2 only create large objects with lo_create(), even when no new_oid is specified. Could you please consider applying the attached patch, that modifies this behaviour?
Comments and changes to this ticket
would you mind raising the question to the mailing list? It will get a much wider attention, including pgpool developers and people who know better the distinction between the two functions (which is not me). Here at best it will be seen by 2 people.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Psycopg is the most used PostgreSQL adapter for the Python programming language. At the core it fully implements the Python DB API 2.0 specifications. Several extensions allow access to many of the features offered by PostgreSQL.