| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: patch: tsearch - some memory diet |
| Date: | 2010-09-07 16:53:42 |
| Message-ID: | 4C866E16.7050604@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> A more general solution would be to have a new MemoryContext
> implementation that does the same your patch does. Ie. instead of
> tracking each allocation, just allocate a big chunk, and have palloc()
> return the next n free bytes from it, like a stack. pfree() would
> obviously not work, but wholesale MemoryContextDelete of the whole
> memory context would.
repalloc() will not work too. Such implementation should have possibility to
debug memory allocation/management by using some kind of red-zones or
CLOBBER_FREED_MEMORY/MEMORY_CONTEXT_CHECKING
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-09-07 16:55:35 | Re: proposal: tsearch dictionary initialization hook |
| Previous Message | Pavel Stehule | 2010-09-07 16:47:54 | Re: patch: tsearch - some memory diet |