> This is all clearly part of the large object mess that we were in before
> you fixed large objects.
>
> Do whatever you think is best for the long term. Large objects were so
> terribly fragile in previous releases, we might as well advertise them
> again as now working 100% of the time. If the new behaviour changes
> existing apps, that is OK if the new behaviour is superior. They will
> be thrilled to change their apps if the large object system now works
> better.
>
> It would be different if the old system worked properly.
I have changed lo_read/lo_write so that they run under same memory
context as other LO calls.
---
Tatsuo Ishii