Re: Large object - what's happening?
От | Cath Lawrence |
---|---|
Тема | Re: Large object - what's happening? |
Дата | |
Msg-id | 3D5D5C08-CEC2-11D7-9752-00039390F614@anu.edu.au обсуждение исходный текст |
Ответ на | Re: Large object - what's happening? (Warwick Hunter <whunter@agile.tv>) |
Ответы |
Re: Large object - what's happening?
|
Список | pgsql-novice |
On Friday, August 15, 2003, at 09:19 AM, Warwick Hunter wrote: > Cath >> I get a python error: >> _pg.err: can't create large object >> In the postmaster log is a one-liner: >> ERROR: lo_lseek: invalid large obj descriptor (0) > Make sure that you are doing the large object manipulation > inside a transaction. I saw this type of error from the > C interface when I forgot to wrap it in a transaction. Thanks for the tip, but how do I do this? I have pygresql 3.3 and have gone through the readme thoroughly, and it says nothing about it. I assumed each call to the database must be a transaction. > It could also be caused by permissions. I think your > database user needs some special priveleges to be able > to create large objects. It's not this - when I am in command line psql mode I can use \lo_import, and it works fine. It's just my python script that fails. thanks C Cath Lawrence, Cath.Lawrence@anu.edu.au Senior Scientific Programmer, Centre for Bioinformation Science, John Curtin School of Medical Research (room 4088) Australian National University, Canberra ACT 0200 ph: (02) 61257959 mobile: 0421-902694 fax: (02) 61252595
В списке pgsql-novice по дате отправления: