Re: Backend memory dump analysis

Teodor Sigaev <teodor@sigaev.ru>

From: Teodor Sigaev <teodor@sigaev.ru>

To: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2018-03-23T20:51:41Z

Lists: pgsql-hackers

Hi!

Some help you could get from
https://github.com/postgrespro/memstat

Vladimir Sitnikov wrote:
> Hi,
> 
> I investigate an out of memory-related case for PostgreSQL 9.6.5, and it 
> looks like MemoryContextStatsDetail + gdb are the only friends there.
> -- 
Teodor Sigaev                      E-mail: teodor@sigaev.ru
                                       WWW: http://www.sigaev.ru/

Commits

Add memory context identifier to portal context
- 94c1f9ba11d1 11.0 landed
Rename MemoryContextCopySetIdentifier() for clarity
- bbca77623fb5 11.0 landed
Allow memory contexts to have both fixed and variable ident strings.
- 442accc3fe0c 11.0 landed
Rethink MemoryContext creation to improve performance.
- 9fa6f00b1308 11.0 cited