From: Tomas Vondra <tomas@vondra.me>
To: Mathias, Renci <rmathias@informatica.com>
To: Yeddula, Madhusudhan reddy [CONTINGENT WORKER] <myeddula@informatica.com>
To: Sahu, Abhisek Kumar <absahu@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, 19 Aug 2024 16:06:57 +0200
Message-ID: <aa31e5dc-0790-48ed-91f2-5d369b0dbeab@vondra.me> (raw)
In-Reply-To: <DM6PR03MB41388C42F0015A43618FDAF9C38C2@DM6PR03MB4138.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>
<DM6PR03MB35009F3FD392BD4A6D263480D3872@DM6PR03MB3500.namprd03.prod.outlook.com>
<DM6PR03MB41388C42F0015A43618FDAF9C38C2@DM6PR03MB4138.namprd03.prod.outlook.com>
On 8/19/24 09:19, Mathias, Renci wrote:
> Hi @Yeddula, Madhusudhan reddy <mailto:myeddula@informatica.com>,
>
> Post re-running the operations, the repository experienced downtime
> after 32 hours and the PID was subsequently changed.
>
>
>
> Here are the details of the run:
>
> * *Run Start Time:* 14th Aug 8:00 PM
> * *Operation Failure:* 15th Aug 8:21 AM (The repository PID 16320 did
> not change and the operation hang)
> * *All Operations Hang:* 16th Aug 10:38 AM
> * *Repository PID Change:* 16th Aug 11:01 AM (PID changed to 10544)
>
>
>
> Below is the screenshot for your reference with reference to Operation
> Failure*:* 15th Aug 8:21 AM
>
>
> Attached is the file with reference to Repository Logs.
>
> Could you please investigate the DB server logs on your end and address
> the queries raised by the PostgreSQL team? Your prompt attention to this
> issue would be of great help.
>
I'm sorry, but those errors / logs are apparently from some proprietary
Informatica product. I doubt anyone here is going to trawl 7.5MB of
verbose logs in search of what might have gone wrong. It's not even
clear to me what should we be looking for and at what time. You'll have
to do that yourself and tell us what the interesting bits are.
In my previous reply from August 12 I asked for a number of things (what
query was running/failed, explain plan, info on memory usage, info on
config parameters, ...). AFAIK we got exactly zero of those responses.
I'm sorry, but that's pretty crucial information for issues like this. I
doubt anyone will be able to help you until you provide that.
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, rmathias@informatica.com, myeddula@informatica.com, absahu@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: <aa31e5dc-0790-48ed-91f2-5d369b0dbeab@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