Re: plperl doesn't release memory
| От | Greg Stark |
|---|---|
| Тема | Re: plperl doesn't release memory |
| Дата | |
| Msg-id | 877jjw4mwd.fsf@stark.xeocode.com обсуждение исходный текст |
| Ответ на | Re: plperl doesn't release memory (Dan Sugalski <dan@sidhe.org>) |
| Ответы |
Re: plperl doesn't release memory
Re: plperl doesn't release memory |
| Список | pgsql-general |
Dan Sugalski <dan@sidhe.org> writes: > Anyway, if perl's using its own memory allocator you'll want to rebuild it > to not do that. You would need to do that if you wanted to use a debugging malloc. But there's no particular reason to think that you should need to do this just to work properly. Two mallocs can work fine alongside each other. They each call mmap or sbrk to allocate new pages and they each manage the pages they've received. They won't have any idea why the allocator seems to be skipping pages, but they should be careful not to touch those pages. -- greg
В списке pgsql-general по дате отправления: