Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbDaJ-00EurS-3z for pgsql-admin@arkaria.postgresql.org; Tue, 06 Aug 2024 06:22:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sbDaG-005Z1o-OQ for pgsql-admin@arkaria.postgresql.org; Tue, 06 Aug 2024 06:22:12 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbDaG-005Z1Y-Ch for pgsql-admin@lists.postgresql.org; Tue, 06 Aug 2024 06:22:12 +0000 Received: from mail-oo1-xc34.google.com ([2607:f8b0:4864:20::c34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sbDaE-003Pny-5b for pgsql-admin@lists.postgresql.org; Tue, 06 Aug 2024 06:22:11 +0000 Received: by mail-oo1-xc34.google.com with SMTP id 006d021491bc7-5d5b850d969so225373eaf.0 for ; Mon, 05 Aug 2024 23:22:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722925328; x=1723530128; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fFPdH65TOWSmX+8XrQpzwNK5uXpysV6wf24nKmTqKxU=; b=CJ87ziVvJMZ1MjOC7QhgPSeYoXukNgW6XEeB652A8g4V3xWvWSfSB5kGzn2Jcl0zuS wMayAzncdPlvdT4FsnhsUBDljLu7748EfV9ZgWlaakZTbWvF+iAvl9kVIJ1xncBFgi8X zVOGPrHpgq4waBc3zIMg2jXHaWavS4ZcjrvfWNlhFZ3UofjdN+P7Vp/i6foyYkNOaEcT rGhQuBBb9WM4LCdR+ERtR7LA5JgEHqEAasxuI7/7wWk7px9MCh8v4hThH1CTMF/F9Kmt WYENN5Kgcyz09P72F41Q9G3uaxuc2dYx1m64uBSdjSyalOql/Oq7RN1KtaOA9M3/yDyQ +eCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722925328; x=1723530128; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fFPdH65TOWSmX+8XrQpzwNK5uXpysV6wf24nKmTqKxU=; b=GedSh96FVOLwK1iE5wHj1SUV2jFiXG4WyV/EL1Ut2q9JiTdAwjpPBW6DylGSJJ0ceY PdJqLRuURaQhgA1G1lNEUIma7FR+fwFGAJJChRYs9ILhsGhSg8DPjOjhEeQd5gfnJTfD pGQr/mPM2yVvLGnK9fPRpKoKsDwXZ+r58H2UxGHmdgF+Je/9kbrQ+phw9g1OgcGPr5mc JKA3HBJrawiBHi2dtmgVyllvrLJIDp+SdU1mvo9tGKBdcFKuaqCrGcqfa/Prju9M+XTo wcnI+8sTjLGglpAQJWiQNQwLKdaGrbnUhOh2kdyeN6d+Pk2zvnoJ/1KMAbBAd/Y6BIit 9p7g== X-Gm-Message-State: AOJu0YzoFjWXBPOjXBdaDvro0qDZeMPYjI0c8QyHkQqgjugpg/OG7zSR NehHmsCNv9yA3TNFiMYfVgG5xbw7DIM052QzJrEGt0E1BzsThlvPo4be2c942GON+6BabOYyXzv UWwLpFZ51spqKaYi4lQ+Y6XMhlg== X-Google-Smtp-Source: AGHT+IGOdwUTWZVVvcQ929KWORLlXVmf5j2Tj8WPpHajep6MI5nuYdO7sb6DLsp0D63qyUMgxMgrv88GwSX9CXc949Q= X-Received: by 2002:a05:6870:f14a:b0:23c:bc3a:6ccb with SMTP id 586e51a60fabf-26891d21fb6mr17576806fac.19.1722925328036; Mon, 05 Aug 2024 23:22:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: khan Affan Date: Tue, 6 Aug 2024 11:21:42 +0500 Message-ID: Subject: Re: Connection exceeded alert. To: Rajesh Kumar Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="00000000000026fac5061efdd00f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000026fac5061efdd00f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Rajesh, To effectively troubleshoot this issue, please share your current PostgreSQL configuration values for shared_buffers, work_mem, and maintenance_work_mem. Additionally, please provide details about the application generating these queries. Are they triggered by POST or GET requests? To gain deeper insights into query performance, execute the following commands: EXPLAIN (ANALYZE, BUFFERS) ; SELECT pid, usename, query, state, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event IS NOT NULL; These commands will help identify performance bottlenecks and resource contention. On Tue, Aug 6, 2024 at 9:32=E2=80=AFAM Rajesh Kumar wrote: > Hi all, > > I have been trying to find a steps or solution for past 1 year once we > received a connection exceeded alert. Couldn't get any answer from anybod= y > or internet so far. > > Today I checked a pgbadger report and matched the timeline and found > that, at that time of sudden connection hike (not normal), there were 3 > queries running at that time (2 update queries on table a , took 5s each, > one insert query on table b which took 2.5mns). > > Anybody provide me steps what all I have to do 1. At that time of > connection hike 2. If I am been asked to check after sometime as connecti= on > dropped to analyse. > --00000000000026fac5061efdd00f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Rajesh,

To effectively troubleshoot this issue= , please share your current PostgreSQL configuration values for shared_buff= ers, work_mem, and maintenance_work_mem.

Additionally, please provide= details about the application generating these queries. Are they triggered= by POST or GET requests?

To gain deeper insights into query performa= nce, execute the following commands:

EXPLAIN (ANALYZE, BUFFERS) <= your_query>;

SELECT pid, usename, query, state, wait_event_type, = wait_event
FROM pg_stat_activity
WHERE wait_event IS NOT NULL;
These commands will help identify performance bottlenecks and resource con= tention.=C2=A0=C2=A0


On Tue, Aug 6, 2024 at 9:32=E2=80=AFAM Rajesh= Kumar <rajeshkumar.dba09= @gmail.com> wrote:
Hi all,

I have been trying to find a steps or solution for past 1 year once = we received a connection exceeded alert. Couldn't get any answer from a= nybody or internet so far.

Today I checked a pgbadger report and=C2=A0 matched the timeline and fou= nd that, at that time of sudden connection hike (not normal), there were 3 = queries running at that time (2 update queries on table a , took 5s each, o= ne insert query on table b which took 2.5mns).

<= /div>
Anybody provide me steps what all I have to do 1. At= that time of connection hike 2. If I am been asked to check after sometime= as connection dropped to analyse.
--00000000000026fac5061efdd00f--