]> granicus.if.org Git - postgresql/commit
Revise large-object access routines to avoid running with CurrentMemoryContext
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 26 Apr 2006 00:35:35 +0000 (00:35 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 26 Apr 2006 00:35:35 +0000 (00:35 +0000)
commitabee2cdb1e9788056c58e77fc2e6c508a5160429
tree42dc6482b096e83be9e8d698b2dc85e875ee8761
parent4454eead14a9c96321bde15d0de7615d7c659dad
Revise large-object access routines to avoid running with CurrentMemoryContext
set to the large object context ("fscxt"), as this is inevitably a source of
transaction-duration memory leaks.  Not sure why we'd not noticed it before;
maybe people weren't touching a whole lot of LOs in the same transaction
before the 8.1 pg_dump changes.  Per report from Wayne Conrad.

Backpatched as far as 8.1, but the problem doubtless goes all the way back.
I'm disinclined to spend the time to try to verify that the older branches
would still work if patched, seeing that this code was significantly modified
for 8.0 and again for 8.1, and that we don't have any trouble reports before
8.1.  (Maybe the leaks were smaller before?)
src/backend/libpq/be-fsstubs.c
src/backend/storage/large_object/inv_api.c
src/include/storage/large_object.h