Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1npMbU-0000yu-OB for pgsql-performance@arkaria.postgresql.org; Fri, 13 May 2022 04:08:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1npMbT-0005pl-JB for pgsql-performance@arkaria.postgresql.org; Fri, 13 May 2022 04:08:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1npMbT-0005pV-6s for pgsql-performance@lists.postgresql.org; Fri, 13 May 2022 04:08:35 +0000 Received: from mail-qt1-x835.google.com ([2607:f8b0:4864:20::835]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1npMbP-0003Ar-OQ for pgsql-performance@postgresql.org; Fri, 13 May 2022 04:08:34 +0000 Received: by mail-qt1-x835.google.com with SMTP id p4so5976343qtq.12 for ; Thu, 12 May 2022 21:08:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Cz18KrGd3B04nXELMvi1aBX4/4Sb6INaARIkfSewcdA=; b=yZdzxk7UqQyUm7gS7Aafc/AwSMbL4W2/DZWMNVVe/q3xepZnuxn+jtFDfTsDFjZwBg PfDkKYL7gex79s2GqMvmANpleDjc3Fm34HccX/UdvksEFKgw+wbcyRzfjXeEUdBsJcF1 Y190iLrizsUDKXxaufaFtKHPhg/UUXbCSsQp2grldPxKruBqs5GV2NoKnh2HYpBuS40r VE6cKxtsyOlmpTB/jcLchp13Hr29WMRFf7TPU9JUJ4yIxbrhZie/3UanHz1MLyzyxKFR uWI5kwr1qWJtt66DOyzEgKGiYKm3RCKMN6wC58t5cCjdC9GhcwrbEk++sjOMIQM9Ggx3 oVvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Cz18KrGd3B04nXELMvi1aBX4/4Sb6INaARIkfSewcdA=; b=ZaLcnB+RiW5DGiNyCssq+MFuLmEVdARH6EcqO7hI2yEMncTwSA3MspQV2Htp0Wbn01 WyJVTBRrWRPp9TeST+EfB24lTfIP1sVpxbrIz1sOw4oxdtaIY9uP4vBFimCZLkv9wOjO A9LmOk4+QffTmuVaDGPZgMHDW6jv5LR1ZiHFGcBBnGawP9evysI+KUuK4LDBdzJfs+kT 2LEZhV/9kuiY/rschUbHBB6zNusqEh/GTNAduRg+6ReC8RqEzach9X+UWxbssy2pnbz/ 22pdV1tjeDZp08BXJ6jIjkD0W83wZIarnxY9YSZ45wzpUot49Kk3cJroVlZULG9GWMVD mP1Q== X-Gm-Message-State: AOAM530W+dlH4/DqG6Hm3ZFNaCM+RaXQcKlDyKPEFVOutVXtieas1nyr xlhZevU1YPRKkieobfUZyqocBA== X-Google-Smtp-Source: ABdhPJwk2Ixg5aTiy22zyK0V1iqNWPK7gzeevltzoIhOHZNR0sNoI65qh84q1mmK0vHKQeBr+xDxrw== X-Received: by 2002:a05:622a:5d4:b0:2f3:cdb0:816a with SMTP id d20-20020a05622a05d400b002f3cdb0816amr2905350qtb.310.1652414909860; Thu, 12 May 2022 21:08:29 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id l29-20020ac84cdd000000b002f3d52d57bcsm864476qtv.26.2022.05.12.21.08.29 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 May 2022 21:08:29 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 59196800B67; Thu, 12 May 2022 23:08:28 -0500 (CDT) Date: Thu, 12 May 2022 23:08:28 -0500 From: Justin Pryzby To: Sudhir Guna Cc: pgsql-performance@postgresql.org Subject: Re: DB connection issue suggestions Message-ID: <20220513040827.GQ19626@telsasoft.com> References: <20220510181540.GC19626@telsasoft.com> <20220511190911.GO19626@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk If the problem occurs gradually (like leaking 20 connections per hour during ETL), you can check pg_stat_activity every hour or so to try to observe the problem before all the connection slots are used up, to collect diagnostic information. Alternately, leave a connection opened to the DB and wait until all connection slots *are* used up, and then check pg_stat_activity. That will take longer, and you'll have more information to weed through. What messages are in the server's log ? v11.2 is years old and hundreds of bugfixes behind. Since you ran into this problem anyway, why not run 11.16, which was released today ? How did you install postgres 11 ? From source or from packages ? Which packages ? The semi-official PGDG RPM packages are available here: https://yum.postgresql.org/ -- Justin