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 1sbBsF-00Eh06-0N for pgsql-admin@arkaria.postgresql.org; Tue, 06 Aug 2024 04:32:38 +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 1sbBsC-002Nuq-Du for pgsql-admin@arkaria.postgresql.org; Tue, 06 Aug 2024 04:32:36 +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 1sbBsC-002Ntj-2A for pgsql-admin@lists.postgresql.org; Tue, 06 Aug 2024 04:32:36 +0000 Received: from mail-lj1-x233.google.com ([2a00:1450:4864:20::233]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sbBs5-003P0A-HN for pgsql-admin@lists.postgresql.org; Tue, 06 Aug 2024 04:32:35 +0000 Received: by mail-lj1-x233.google.com with SMTP id 38308e7fff4ca-2ef1c12ae23so2529981fa.0 for ; Mon, 05 Aug 2024 21:32:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722918746; x=1723523546; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=gYi+SXB5mgNQi8KkWhJDHksJQc2HRXqOYS7/g0VCtqs=; b=FjhcmeJHs9YsTqDz5fmd1A/yJeDmT0C6TWXhN4IhPc2NygV6HjLRC+FQ5ij9B/zm51 XS9NZ7pDdfa7iNzhkRkNWit4wK9mu/iWBjpiX5CQObpxdNX7wzu5bqdUXBfgAouosiZP YW1IkVmkTDDSHs2JY2tAHAg4ukeKZBlgsJtmWhTWYnJ2h1B0J8R55E+ur6/UMMTJGZ6p sLtQnI2h8BOlQ4xH1JGuG/iO/Isau2cFww+IPBEZdAcNK2gHAlp1hKLHc92nQWGPSO4b MxXhrjbz/pnGC7Kuwl1p+uWfvwsECcHhs76yHMkIWkwwTGWOMsFpISB+jigGboHL6a/z jHUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722918746; x=1723523546; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=gYi+SXB5mgNQi8KkWhJDHksJQc2HRXqOYS7/g0VCtqs=; b=v5hbpr9gooyqPMJxro315HigmpQlwDbP7LB4vHv3DZuuLdWEql1oSfFYePNaVpqs4M 9C7uNOJPfZ9TYkIwZ6VL4vS8Wg/jdw90Jz2VySYWeJ2gtDGZ2+6EyAKrTgTgKE83y1uV k6xQ6YMwoizVa2jrtd4PVHPAMFBSz5aN+r0+Bv+Nao3swpVsGyNKtXNlOpj3trezi/2E Nz5Elw/KA1WVAHrzzGTdcqi2apL2jGg71m4htYeZV+MhfYngsWB3rxaDNMK64hcBNgoY vF6NERRUVeKz82WUVqmYzBIndyNuisyZgXohQf2X5mn9HbWWb7R4KGx3JBoqtRvLh+kC s7dg== X-Gm-Message-State: AOJu0YzKhIwmqqgNmlQeQfndi49guMJDCKLaLxBX1TeOPzO1zzSd6nfm ovekIg/Pqm1GqgAuMGnbNqwMqGQRVbdrwKll+H2lux3515NexXIiAEPwTO6rQ4ELw27ZbIrEEAE kGWVbBGJ4PWVQGS4S2VEotLR6rHAQywOh X-Google-Smtp-Source: AGHT+IEyHTd65AhXrdHs6fBy2rNx/K8LoEnt7AqRInXLhtGhmlPiq8K2yQUsxZDf/IGhCD22nW9rk+qeT7imxmXEvBo= X-Received: by 2002:a2e:968c:0:b0:2ef:2525:be90 with SMTP id 38308e7fff4ca-2f15aaf6231mr103068201fa.31.1722918745287; Mon, 05 Aug 2024 21:32:25 -0700 (PDT) MIME-Version: 1.0 From: Rajesh Kumar Date: Tue, 6 Aug 2024 10:02:14 +0530 Message-ID: Subject: Connection exceeded alert. To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000ca33fc061efc479c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ca33fc061efc479c Content-Type: text/plain; charset="UTF-8" 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 anybody 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 connection dropped to analyse. --000000000000ca33fc061efc479c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

I ha= ve 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 anybody or i= nternet so far.

Today I = checked a pgbadger report and=C2=A0 matched the timeline and found that, at= that time of sudden connection hike (not normal), there were 3 queries run= ning at that time (2 update queries on table a , took 5s each, one insert q= uery 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 connect= ion dropped to analyse.
--000000000000ca33fc061efc479c--