From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Locks analyze
Date: Thu, 12 Oct 2023 20:21:34 -0600
Message-ID: <ED834456-7DAF-4A33-B9B3-E86BEF67D9BE@elevated-dev.com> (raw)
In-Reply-To: <CAJk5AtaHsNNp-R3zmeeZ9G06LH_yHXEdCN7TpeR2HTO4Tde7Hw@mail.gmail.com>
References: <CAJk5AtaHsNNp-R3zmeeZ9G06LH_yHXEdCN7TpeR2HTO4Tde7Hw@mail.gmail.com>
> On Oct 12, 2023, at 5:46 PM, Rajesh Kumar <rajeshkumar.dba09@gmail.com> wrote:
>
> How do I analyze locks and resolve it. Is there only one query that helps? This lock issue leading to high connections it seems.
What lock issue? What do you mean leading to high connections?
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-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, rajeshkumar.dba09@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Locks analyze
In-Reply-To: <ED834456-7DAF-4A33-B9B3-E86BEF67D9BE@elevated-dev.com>
* 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