Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Z3UCx-0008RI-Fc for pgsql-general@arkaria.postgresql.org; Fri, 12 Jun 2015 19:01:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Z3UCw-0003aP-S1 for pgsql-general@arkaria.postgresql.org; Fri, 12 Jun 2015 19:01:38 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Z3UCv-0003aI-Mu for pgsql-general@postgresql.org; Fri, 12 Jun 2015 19:01:37 +0000 Received: from nm3-vm8.bullet.mail.ir2.yahoo.com ([212.82.96.97]) by makus.postgresql.org with esmtps (TLS1.0:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Z3UCs-0001qq-BY for pgsql-general@postgresql.org; Fri, 12 Jun 2015 19:01:36 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048; t=1434135690; bh=D0c+NkXtpfn07WOelQqkP3tCNzkjQFP3xKZPklDFUJ0=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=U7/a1rYqe6yByGASqqPRRwfY1hNHwGYhznM91F1hw2t7gr3IxGn1csCYiLgCISFxzpKkVmODR+zK4N4bxv9YXlsNhElKWXhKOZLvmg2Sra4eYcJZa/x4zlE+ZH2QUXUtfXZh0GftBOG/leQZj7hQLWOs3x4+uM4mWcgaEOsTX/YB1jHe4XCscZ9TOpuPWARWsu1pSlfOPDHGKi0nzoHHy+5l9yCggOvugFJtO2BvfceXg+OHJBM4lO2mdB+DsCevHJfOyUBtFSEgBbfrjtnWehj8qxREmHGpZ653ke+geBacMnm9P5m00xUJ0RByvyymWdLAQs1mZI/o2OkDyYTAZA== Received: from [212.82.98.48] by nm3.bullet.mail.ir2.yahoo.com with NNFMP; 12 Jun 2015 19:01:30 -0000 Received: from [212.82.98.85] by tm1.bullet.mail.ir2.yahoo.com with NNFMP; 12 Jun 2015 19:01:30 -0000 Received: from [127.0.0.1] by omp1022.mail.ir2.yahoo.com with NNFMP; 12 Jun 2015 19:01:30 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 826333.75561.bm@omp1022.mail.ir2.yahoo.com X-YMail-OSG: S2aomxQVM1liJpC_GZIy_Ilo40xyMEdqw2OT0qsi6jXJ97SqUxQbZGujwlwlq7H B0iV03P82ajXa9Hi_l5Cu63bTeyZst1hTKc6TZZHvUDEvsF_eTGdTzzxaZ2yxkT7bHzS8E6L4uya m9OfZGsku8xavA6hlxMpttf3hu3_hkVf3Qsd35e093pPr4qTnm_0sp7sX0vIOHn.EF3S80P.vnMc OOoNAfN9ht6Li7ky7GeiwzRqZAYMYaXHy0pFclatkQEAnEUfHrZCfbCIfvPX_dykKPqym5gAkLqo ZXJ.0LblTQUELuM_3ciGmFQKeXJdzYrYG6.Ti6i3u8pIJ.gzxnouQ1Mat7JJJOvE6GygdNpoJg7R MIdh9H_7i3eECFwzRMmMXQs1bnYogbVc6UbMsDVLhQLUNInYInrLHy0EVO1XlcJNZG3PamBX9x8t kV8JRkOXwXq8EanzUSFBTekCuCg8DYAB8RVChvS8GbcXoPtTEGD8FB6jUrFpIix3Biiq9FAUHpy1 Gz9ZJfPwSXSlA Received: by 217.12.9.13; Fri, 12 Jun 2015 19:01:30 +0000 Date: Fri, 12 Jun 2015 19:01:29 +0000 (UTC) From: Glyn Astill Reply-To: Glyn Astill To: "Sheena, Prabhjot" , "pgsql-general@postgresql.org" Message-ID: <870941851.3347884.1434135689729.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <13E39D789E19FF4E9A87F6D456F3F982E90F30@SEAMBX03.sea.corp.int.untd.com> References: <13E39D789E19FF4E9A87F6D456F3F982E90F30@SEAMBX03.sea.corp.int.untd.com> Subject: Re: pg bouncer issue what does sv_used column means MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Length: 1078 X-Pg-Spam-Score: -3.1 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org > From: "Sheena, Prabhjot" >To: "pgsql-general@postgresql.org" ; "pgsql-performance@postgresql.org" >Sent: Friday, 12 June 2015, 18:57 >Subject: [GENERAL] pg bouncer issue what does sv_used column means > > > >Guys we see spike in pg bouncer during the peak hours and that was slowing down the application. We did bump up the connection limit and it is helpful but now we again notice little spike in connection. And one thing that I notice that is different is jump in sv_used value when I run command show pools during problem times > > >Can anyone please explain what value of sv_used means when i run show pools; > > > See the manual: http://pgbouncer.projects.pgfoundry.org/doc/usage.html I believe in this instance "used" is interpreted as idle server connections that are in the process of being (periodically) health checked before being made available to clients again. A stab in the dark would be to check what query you're using in server_check_query. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general