From: Tom Lane <tgl@sss.pgh.pa.us>
To: kurt@roeckx.be
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16707: Memory leak
Date: Mon, 09 Nov 2020 16:34:33 -0500
Message-ID: <1999972.1604957673@sss.pgh.pa.us> (raw)
In-Reply-To: <16707-f5df308978a55bf8@postgresql.org>
References: <16707-f5df308978a55bf8@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> It seems that since I switched from PostgreSQL 9.5 to 12, I started to have
> a memory leak.
Could you maybe collect a memory map from one of the bloated processes?
It'd go something like
* attach to process with gdb
* "call MemoryContextStats(TopMemoryContext)"
* quit gdb
* look in postmaster log for memory dump
You probably need to have debug symbols installed for step 2 to work.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, kurt@roeckx.be, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16707: Memory leak
In-Reply-To: <1999972.1604957673@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox