| From: | "Graeme B(dot) Bell" <graeme(dot)bell(at)nibio(dot)no> |
|---|---|
| To: | Bram Van Steenlandt <bram(at)diomedia(dot)be>, "pgsql-performance(at)postgresql(dot)org list" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: large object write performance |
| Date: | 2015-10-08 13:10:00 |
| Message-ID: | E776D57D-2F9D-4DD1-AF83-696F93A31A50@skogoglandskap.no |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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() libpq functions.”
>>
>> 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 way to 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bram Van Steenlandt | 2015-10-08 14:13:58 | Re: large object write performance |
| Previous Message | Bram Van Steenlandt | 2015-10-08 12:29:28 | Re: large object write performance |