>>>>> "Sean" == Sean Lyndersay <lynders@hcs.harvard.edu> writes:
Sean> On Mon, 9 Jun 1997, Bruce Momjian wrote:
>> >
>> > The ToDo list includes the following as an enhancement in
>> > version 6.1:
>> > Large objects
>> > overwriting blocks has problems there are other
>> > problems, too. Fix large object mapping scheme not to
>> > stuff everything as files in a single directory
>> >
>> > Does this mean that large objects work now? If so, is the
>> > libpq++ testlo.cc example supposed to work?
>>
>> As the maintainer of the todo list, I can say, "I don't know."
>>
>> The TODO list is only a list of REPORTED problems.
>>
Sean> Okay, how about this:
Sean> -- copy start --
Sean> CHANGES IN THE 6.1 RELEASE
Sean> Bug Fixes ---------
Sean> [snip] large object fixes(Sven)
Sean> -- copy end --
Sean> guess we'll wait until sven reads and comments. :)
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.
Ray
------------------------------
