Re: Backend memory dump analysis - Mailing list pgsql-hackers

From Vladimir Sitnikov
Subject Re: Backend memory dump analysis
Date
Msg-id CAB=Je-H5vtNs_kjrEsktvVeZ_nfWPJRMp2e7-rhE+iw_CzT8EA@mail.gmail.com
Whole thread Raw
In response to Re: Backend memory dump analysis  (Andres Freund <andres@anarazel.de>)
Responses Re: Backend memory dump analysis  (Andres Freund <andres@anarazel.de>)
List 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 by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: Re: csv format for psql
Next
From: Andres Freund
Date:
Subject: Re: Backend memory dump analysis