#88 ✓ resolved

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?

Thanks, Giovanni.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

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.

Shared Ticket Bins