Memory leaks for large objects - Mailing list pgsql-hackers

From Maurice Gittens
Subject Memory leaks for large objects
Date
Msg-id 00f901bd3af3$1bdd6500$fcf3b2c2@caleb..gits.nl
Whole thread Raw
Responses Re: [HACKERS] Memory leaks for large objects  (Peter T Mount <psqlhack@maidast.demon.co.uk>)
List pgsql-hackers
Ok,

I think large objects are leaking memory because the large object functions
in the backend use their own GlobalMemoryContext (called Filesystem), which
(according to a quick grep) is never freed.

Supposing this is true and I ensure that the large object subsystem always
uses the current memory context for it's memory allocations.

What might go wrong? (Or why did the designers decide to use a
GlobalMemoryContext for large objects?).

I simple don't understand why one would create a special memory context
for large objects without some special reason.
Or should I just try it and see is anything breaks?

Thanks for any comments.
Maurice



pgsql-hackers by date:

Previous
From: "Vadim B. Mikheev"
Date:
Subject: Re: AW: [HACKERS] Re: Subselects open issue Nr. 5
Next
From: "Frederick W. Reimer"
Date:
Subject: RE: [HACKERS] Re: [PORTS] v6.3 release ToDo list and supported p