Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bGTlG-0007gZ-2S for pgsql-admin@arkaria.postgresql.org; Fri, 24 Jun 2016 16:15:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bGTlF-0001Di-LP for pgsql-admin@arkaria.postgresql.org; Fri, 24 Jun 2016 16:15:17 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bGTgz-0007WX-Km for pgsql-admin@postgresql.org; Fri, 24 Jun 2016 16:10:53 +0000 Received: from smtp82.iad3a.emailsrvr.com ([173.203.187.82]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bGTgv-0005Pt-La for pgsql-admin@postgresql.org; Fri, 24 Jun 2016 16:10:52 +0000 Received: from smtp19.relay.iad3a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp19.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id DF5A81804C3 for ; Fri, 24 Jun 2016 12:10:40 -0400 (EDT) X-SMTPDoctor-Processed: csmtpprox beta Received: from smtp19.relay.iad3a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp19.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id D9BA7180385 for ; Fri, 24 Jun 2016 12:10:40 -0400 (EDT) Received: from smtp192.mex08.mlsrvr.com (unknown [74.205.9.160]) by smtp19.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTPS id C99A71802D8 for ; Fri, 24 Jun 2016 12:10:40 -0400 (EDT) X-Sender-Id: tkirstine@firstbasesolutions.com Received: from smtp192.mex08.mlsrvr.com ([UNAVAILABLE]. [74.205.9.160]) (using TLSv1.2 with cipher AES256-SHA) by 0.0.0.0:25 (trex/5.5.4); Fri, 24 Jun 2016 12:10:42 -0400 Received: from MBX12A-IAD3.mex08.mlsrvr.com (172.29.17.37) by MBX02B-IAD3.mex08.mlsrvr.com (172.29.17.15) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 24 Jun 2016 12:10:42 -0400 Received: from MBX12B-IAD3.mex08.mlsrvr.com (172.29.17.42) by MBX12A-IAD3.mex08.mlsrvr.com (172.29.17.37) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 24 Jun 2016 12:10:41 -0400 Received: from MBX12B-IAD3.mex08.mlsrvr.com ([fe80::4c69:fdd0:ae19:de2f]) by MBX12B-IAD3.mex08.mlsrvr.com ([fe80::4c69:fdd0:ae19:de2f%12]) with mapi id 15.00.1178.000; Fri, 24 Jun 2016 12:10:41 -0400 From: Travis Kirstine To: "pgsql-admin@postgresql.org" Subject: superuser_reserved_connections and max_connections Thread-Topic: superuser_reserved_connections and max_connections Thread-Index: AQHRzjHPR8/q/gldWEinb5AfOgY/kQ== Date: Fri, 24 Jun 2016 16:10:41 +0000 Message-ID: <1466784642535.32585@firstbasesolutions.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [205.207.145.254] Content-Type: multipart/alternative; boundary="_000_146678464253532585firstbasesolutionscom_" MIME-Version: 1.0 X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --_000_146678464253532585firstbasesolutionscom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable We were getting a lot of "max connections reached" errors and noticed that = all our users are super users, after some digging I found the superuser_reserved_connections parameter was not set (default to 3) this le= ad to some additional questions: If all my users are superusers are they effectively limited to the number = of connections defined in the superuser_reserved_connections parameter? Is there any significant difference between a superuser and non-superuser c= onnection? Any additional insight would be great. --_000_146678464253532585firstbasesolutionscom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable


We were getting a lot of "max connections reached" errors and = noticed that all our users are super users, after some digging I found the&= nbsp;

superuser_reserved_connections parameter was not set (default to 3) this= lead to some additional questions:


If all my users are  superusers are they effectively limited to the= number of connections defined in the 

superuser_reserved_connections  parameter?


Is there any significant difference between a superuser a= nd non-superuser connection?


Any additional insight would be great.

--_000_146678464253532585firstbasesolutionscom_--