Re: [HACKERS] Large objects

> >
> > I've been pounding on large objects for the last few days.  It's
> > pretty stable, much more so than earlier versions.  However, I've only
> > tested the lo_import, lo_export SQL functions, and the lo_read,
> > lo_write, and lo_create functions in libpq.  They seem to work well
> > now.
> >
> >     Sean> meanwhile, i'll see if i can find the problem. For those
> >     Sean> interested, the test program failes when trying to read the
> >     Sean> large object out of the database with the following message:
> >     Sean>  "OTICE:LockRelease: locktable lookup failed, no lock"
> >
> > I've seen this.  I think this means either you have nested begin/end
> > transactions or forgot a begin/end transaction block, but have not
> > checked into it yet.
> >

Can't be that. I'm using the testlo.cc program in the libpq++/examples
directory. It has a begin and an end command. For reference, I'm using the
snapshot day before yesterday.

My preference would be to have these large object patches asap. It seems
that they are broken right now. Either that or libpq++ is broken. If
Raymond is having no problems with libpq, then I can debug libpq++ and see
what's happening. I'd rather not repeat anything he's done.

thanks
sean

________________________________________________________________________
Sean Lyndersay                        Time is natures way of making sure
lynders@hcs.harvard.edu                 things don't happen all at once.
________________________________________________________________________
[finger for all other info]          http://www.hcs.harvard.edu/~lynders

------------------------------