From: | Cath Lawrence <Cath(dot)Lawrence(at)anu(dot)edu(dot)au> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Large object - what's happening? |
Date: | 2003-08-15 01:46:07 |
Message-ID: | 3D5D5C08-CEC2-11D7-9752-00039390F614@anu.edu.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)Lawrence(at)anu(dot)edu(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2003-08-15 04:45:58 | Re: COLLATE |
Previous Message | Girish Bajaj | 2003-08-14 23:39:17 | Qualified Names |