From: | "Maurice Gittens" <mgittens(at)gits(dot)nl> |
---|---|
To: | "PostgreSQL-development" <hackers(at)postgreSQL(dot)org> |
Subject: | Memory leaks for large objects |
Date: | 1998-02-16 15:54:05 |
Message-ID: | 00f901bd3af3$1bdd6500$fcf3b2c2@caleb..gits.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Meskes, Michael | 1998-02-16 16:00:13 | RE: [HACKERS] Re: [PORTS] v6.3 release ToDo list and supported p |
Previous Message | Zeugswetter Andreas SARZ | 1998-02-16 14:43:26 | AIX 4.1.5 is OK as of snapshot 16.2.98 |