From: Tomas Vondra <tomas@vondra.me>
To: Sahu, Abhisek Kumar <absahu@informatica.com>
To: Yeddula, Madhusudhan reddy [CONTINGENT WORKER] <myeddula@informatica.com>
To: Mathias, Renci <rmathias@informatica.com>
To: Daniel Gustafsson <daniel@yesql.se>
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
To: Sachan, Vishal <vsachan@informatica.com>
Cc: Kumar, Gaurav <gaurkumar@informatica.com>
Cc: Nayak, Deepak Vaikunta <dnayak@informatica.com>
Subject: Re: BUG #18569: Memory leak in Postgres Enterprise server
Date: Mon, 12 Aug 2024 10:44:27 +0200
Message-ID: <65321f11-d8e1-4094-abbe-41b593a49801@vondra.me> (raw)
In-Reply-To: <PH0PR03MB66551AB89EA17EB22C3C7C45D6852@PH0PR03MB6655.namprd03.prod.outlook.com>
References: <18569-ba603937af37b1b6@postgresql.org>
<4B5860EC-DBDB-464A-B744-C5091BF71659@yesql.se>
<PH0PR03MB6655A2DA4083AA506FF34FB9D6BF2@PH0PR03MB6655.namprd03.prod.outlook.com>
<DM6PR03MB41383627807E6B70234F0F0AC3B82@DM6PR03MB4138.namprd03.prod.outlook.com>
<DM6PR03MB3500DA4C636F1FC32C6C4C80D3B82@DM6PR03MB3500.namprd03.prod.outlook.com>
<PH0PR03MB66551AB89EA17EB22C3C7C45D6852@PH0PR03MB6655.namprd03.prod.outlook.com>
Hi Abhisek,
On 8/12/24 07:37, Sahu, Abhisek Kumar wrote:
> Hi Daniel,
>
> Kindly let us know if you have any updates.
>
It's hard to say what happened, based on the information provided so
far. It might be that there really is a bug / memory leak, or maybe the
selected query plan is not great, or maybe there's a configuration
issue. We'll need more information to find out.
1) What query was the failed backend running? Was it a big long-running
query (e.g. in ETL/BI application), or many small OLTP queries?
2) Do you know what execution plan was used?
3) If you rerun the query, does the memory usage grow the same way? This
would allow us to collect important data. For example, it would be very
useful if you could attach a debugger to a backend consuming a lot of
memory, and get memory context stats.
4) Can you share the configuration parameters? I think the memory config
is the most interesting one (shared_buffers, work_mem, ...). How much
RAM does the system have?
5) Is this a parallel query? In the snippet from /var/log/messages there
are 3-5 postgres processes that look like they might be parallel workers
(nearly sequential PIDs, same memory pattern).
6) Is this a long-running problem, or did it just start to happen
recently? Perhaps after some change/upgrade?
regards
--
Tomas Vondra
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: tomas@vondra.me, absahu@informatica.com, myeddula@informatica.com, rmathias@informatica.com, daniel@yesql.se, pgsql-bugs@lists.postgresql.org, vsachan@informatica.com, gaurkumar@informatica.com, dnayak@informatica.com
Subject: Re: BUG #18569: Memory leak in Postgres Enterprise server
In-Reply-To: <65321f11-d8e1-4094-abbe-41b593a49801@vondra.me>
* 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