Re: large object write performance - Mailing list pgsql-performance

From Graeme B. Bell
Subject Re: large object write performance
Date
Msg-id E776D57D-2F9D-4DD1-AF83-696F93A31A50@skogoglandskap.no
Whole thread Raw
In response to Re: large object write performance  (Bram Van Steenlandt <bram@diomedia.be>)
Responses Re: large object write performance  (Bram Van Steenlandt <bram@diomedia.be>)
List pgsql-performance
>>
>> http://initd.org/psycopg/docs/usage.html#large-objects
>>
>>
>> "Psycopg large object support *efficient* import/export with file system files using the lo_import() and lo_export()
libpqfunctions.” 
>>
>> See *
>>
> I was under the impression they meant that the lobject was using lo_import and lo_export.
> I can't seem to find how to use lo_import en export, I searched google and came to the conclusion the lobject was the
wayto go. 
> >>> x.lo_import()
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> AttributeError: 'psycopg2._psyco

Bram,

I recommend posting this as a question on a python/psycopg mailing list, for advice.
You are probably not the first person to encounter it.

Graeme Bell



pgsql-performance by date:

Previous
From: Bram Van Steenlandt
Date:
Subject: Re: large object write performance
Next
From: Bram Van Steenlandt
Date:
Subject: Re: large object write performance