Re: Backend memory dump analysis

Поиск
Список
Период
Сортировка
От Vladimir Sitnikov
Тема Re: Backend memory dump analysis
Дата
Msg-id CAB=Je-H5vtNs_kjrEsktvVeZ_nfWPJRMp2e7-rhE+iw_CzT8EA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Backend memory dump analysis  (Andres Freund <andres@anarazel.de>)
Ответы Re: Backend memory dump analysis  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
Andres>The overhead required for it (in cycles, in higher memory usage due to
additional bookeeping

Does that mean the memory contexts are unparseable? (there's not enough information to enumerate contents)

What if memory dump is produced by walking the C structures?
For instance, I assume statament cache is stored in some sort of a hash table, so there should be a way to enumerate it in a programmatic way. Of course it would take time, however I do not think it creates cpu/memory overheads. The overhead is to maintain "walker" code.

Vladimir

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

Предыдущее
От: Fabien COELHO
Дата:
Сообщение: Re: Re: csv format for psql
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Backend memory dump analysis