Re: BUG #4496: Memory leak in pg_dump.c?

Поиск
Список
Период
Сортировка
От Zdenek Kotala
Тема Re: BUG #4496: Memory leak in pg_dump.c?
Дата
Msg-id 490AE98C.2060709@sun.com
обсуждение исходный текст
Ответ на Re: BUG #4496: Memory leak in pg_dump.c?  (Aggro <dvice_null@yahoo.com>)
Список pgsql-bugs
Aggro napsal(a):
>> I think all information is collected and they are
>> used for all pg_dump run. It
>> does not make sense to free them. See line 725.
>>
>>         Zdenek
>
> But is the memory freed at some point? E.g. when
> program shuts down? If it is not freed ever, then it
> is a memory leak. I'm interested in this, because
> either you have a memory leak or these is a bug in
> another application called cppcheck which claims that
> you have a memory leak. But if it is too difficult to
> find out, I won't bother you about this anymore as it
> is most likely a minor issue if even that.

Keep in mind that onetime allocated local memory is not reclaimed to OS until
process finished. See sbrk(2) It does not make sense to free memory at the end
(in pg_dump) because it does not have any effect on available memory in OS and
OS clean it soon anyway. I agree that from general point of view it is good to
release unused memory, because process can reuse it. But when you know what you
do then you can break a rule.

        Zdenek


--
Zdenek Kotala              Sun Microsystems
Prague, Czech Republic     http://sun.com/postgresql

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Gabriele Bartolini
Дата:
Сообщение: Docbook DSSSL Stylesheets link is broken
Следующее
От: Zdenek Kotala
Дата:
Сообщение: Re: BUG #4494: Memory leak in pg_regress.c