Re: [HACKERS] Everything leaks; How it mm suppose to work?
В списке pgsql-hackers по дате отправления:
| От | Vadim B. Mikheev |
|---|---|
| Тема | Re: [HACKERS] Everything leaks; How it mm suppose to work? |
| Дата | |
| Msg-id | 352CE149.4756A8D9@sable.krasnoyarsk.su обсуждение |
| Ответ на | Re: [HACKERS] Everything leaks; How it mm suppose to work? ("Maurice Gittens" <mgittens@gits.nl>) |
| Список | pgsql-hackers |
Thomas G. Lockhart wrote: > > > >Does it make sense to have a 'row' context which is released just > > >before starting with a new tuple ? The total number or free is the > > >same but they are distributed over the query and unused memory should > > >not accumulate. > > >I have seen backends growing to 40-60MB with queries which scan a > > >very large number of rows. > > I think this would be appropiate. > > It seems that the CPU overhead on all queries would increase trying to > deallocate/reuse memory during the query. There are lots of places in > the backend where memory is palloc'd and then left lying around after > use; I had assumed it was sort-of-intentional to avoid having extra > cleanup overhead during a query. This problem (introduced in 6.3) is already fixed by Bruce - will be in 6.3.2 Vadim
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера