| From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
|---|---|
| To: | Maurice Gittens <mgittens(at)gits(dot)nl> |
| Cc: | hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Memory leaks? |
| Date: | 1998-02-13 12:31:50 |
| Message-ID: | 34E43D36.547A193B@sable.krasnoyarsk.su |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Maurice Gittens wrote:
>
> - Postgresql Version: 6.3 (recent (this week) snapshop)
> - OS: Linux 2.0.33
> - INSERT's are within BEGIN/END brackets
> - TBL_FREE_CMD_MEMORY is defined in config.h (I guess it's the default).
^^^^^^^^^^^^^^^^ - in 6.3
Well, this means that problem lies in large objects...
I never used them... I assume that new relation and index
is created for each LO. If this is right then we have memory leak
in relation cache (heap_close doesn't flush relation from cache).
Also, as I see now, LO interface uses its own memory context:
TBL_FREE_CMD_MEMORY can't help here -> all allocation must be
freed "manually".
Unfortunately, I haven't time...
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brett McCormick | 1998-02-13 12:40:24 | Re: [HACKERS] v6.3 snapshot core dump |
| Previous Message | Vadim B. Mikheev | 1998-02-13 12:11:26 | Re: [HACKERS] v6.3 snapshot core dump |