Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcEoA-0001Fo-G0 for pgsql-bugs@arkaria.postgresql.org; Mon, 09 Nov 2020 21:34:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kcEo9-00041C-DC for pgsql-bugs@arkaria.postgresql.org; Mon, 09 Nov 2020 21:34:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcEo9-000415-7F for pgsql-bugs@lists.postgresql.org; Mon, 09 Nov 2020 21:34:37 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcEo7-00063C-0v for pgsql-bugs@lists.postgresql.org; Mon, 09 Nov 2020 21:34:36 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0A9LYX9v1999973; Mon, 9 Nov 2020 16:34:33 -0500 From: Tom Lane To: kurt@roeckx.be cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16707: Memory leak In-reply-to: <16707-f5df308978a55bf8@postgresql.org> References: <16707-f5df308978a55bf8@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 09 Nov 2020 21:07:21 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1999971.1604957673.1@sss.pgh.pa.us> Date: Mon, 09 Nov 2020 16:34:33 -0500 Message-ID: <1999972.1604957673@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form 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