Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XLwY6-0004pc-9Y for pgsql-admin@arkaria.postgresql.org; Mon, 25 Aug 2014 15:51:14 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XLwY5-0007G9-Pu for pgsql-admin@arkaria.postgresql.org; Mon, 25 Aug 2014 15:51:13 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XLwY4-0007G3-V0 for pgsql-admin@postgresql.org; Mon, 25 Aug 2014 15:51:13 +0000 Received: from nm29-vm3.bullet.mail.ne1.yahoo.com ([98.138.91.159]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XLwY1-0000Gh-Bl for pgsql-admin@postgresql.org; Mon, 25 Aug 2014 15:51:11 +0000 Received: from [98.138.226.176] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 25 Aug 2014 15:51:07 -0000 Received: from [98.138.88.233] by tm11.bullet.mail.ne1.yahoo.com with NNFMP; 25 Aug 2014 15:51:07 -0000 Received: from [127.0.0.1] by omp1033.mail.ne1.yahoo.com with NNFMP; 25 Aug 2014 15:51:07 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 410812.71540.bm@omp1033.mail.ne1.yahoo.com Received: (qmail 16988 invoked by uid 60001); 25 Aug 2014 15:51:07 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1408981867; bh=4f//sotYZgR3ob5iOIKFOcSHNfKlD6U1FnI+fAMRy3U=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=iKQbs2hFgKTwKcw4U93eGr5xHkJwV4YaEq85Sg4S3+JN41fQuZ0BXx6xnD9AYFcT72aChktequKRyk3B/UM35S6a+UjXGrsOaAZY8aX0FxoNza4llCKfRMT1UIkN/Bdf7XrfnnBVKuifD7enBTWpymYuVsDfE7okjYDb3wzsEms= X-YMail-OSG: JwFX7CoVM1nIWpR6nF3nrQ8y5GyVBdm1iH4eT8M.Ssqgky6 lSFw5.rIwspMWHVG4t8XsPb3bcEJ4867boGX32i9_0zcF3OG0Ehw8gew9OjT rLTVyRTAwQdNTZG0R4VZ5ghj3yUA0dMmDXrAbBvChF7sqU3fKbAsyLFBh9ks KgNxblYx5GH.pT1j5CRSmFAnRuBFMQBYgD7x.opCgTLRLtmLGKXtn8oIXR2i qjC6HAEQnTHqyZ57U99zQQ.Jm7DqX0e.Qw675qW7amT6NZwGLT1hCjEVrsPz wgIiSYYoavXslDchh5NX8WARItOHeAg28PrdzAcTBHlQwaelvarBQ8tfmnLZ RR_eQUXG1dqvJkLqnEe04ufy7TpXtt9uzL_C32EiEdf5sMe3ll_X.SrFaRTF cLedUedTdc.u70f.Gf7gm.fWro615Sszyl2SXsFYRmsgeN8_4Qvk6Ut8Vy1O M_mJ0MP7hkVVfn6LUtLUfr12YkuVUm_U2eH6x.lbpZYXS50qtuWQZAqBsP8O edu_TzuOhzRZVE14bXvRFmd9ouZxXXuJoETj1b21XvETlmhjz4m7mVfamL_a Y03hynKAaN0vDUFXq61cHpIZc4kD4UdwpKDZUqKOgIbq49CmtaJkmzivKBd7 OR0OAdCki9ThMZOx9NgP0wYpemv8- Received: from [24.178.25.147] by web122303.mail.ne1.yahoo.com via HTTP; Mon, 25 Aug 2014 08:51:07 PDT X-Rocket-MIMEInfo: 002.001, RGhydXYgU2h1a2xhIDxkaHJ1dnNodWtsYTgyQGdtYWlsLmNvbT4gd3JvdGU6Cgo.IE90aGVyIGluZm9ybWF0aW9uYWwgZGV0YWlscyBhYm91dCBjb25maWd1cmF0aW9ucyBhcmU6Cgo.IHNoYXJlZF9idWZmZXJzID0gODBHQgo.IHRlbXBfYnVmZmVycyA9IDJHQgo.IHdvcmtfbWVtID0gMkdCCj4gbWFpbnRlbmFuY2Vfd29ya19tZW0gPSAxNkdCCgpXZWxsLCBhdCB0aGUgZGVmYXVsdCBtYXhfY29ubmVjdGlvbnMgb2YgMTAwIHRoYXQgY291bGQgZWFzaWx5CnJlc3VsdCBpbiB0aGUgc2VydmVyIHRyeWluZyB0byABMAEBAQE- X-Mailer: YahooMailWebService/0.8.201.700 References: <15C963C4-539B-4A88-9C21-54C3221FD1D7@gmail.com> Message-ID: <1408981867.41595.YahooMailNeo@web122303.mail.ne1.yahoo.com> Date: Mon, 25 Aug 2014 08:51:07 -0700 From: Kevin Grittner Reply-To: Kevin Grittner Subject: Re: Problems with PG 9.3 To: Dhruv Shukla , Albe Laurenz Cc: "jayknowsunix@gmail.com" , "pgsql-admin@postgresql.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable 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 Dhruv Shukla wrote: > Other informational details about configurations are: > shared_buffers =3D 80GB > temp_buffers =3D 2GB > work_mem =3D 2GB > maintenance_work_mem =3D 16GB Well, at the default max_connections of 100 that could easily result in the server trying to allocate about 567GB of RAM.=A0 If your number of connections is more than 100, adjust proportionally higher.=A0 If the server doesn't have that, you could see extreme swapping or various other problems as the OS tries to survive. > effective_cache_size =3D 130GB And the planner will be generating plans based on the assumption that the combination of shared_buffers and the OS cache will have this much RAM available for caching, so if you have max_connections =3D 100 this configuration would only make sense on a machine with RAM of 617GB or more, plus whatever is needed for the OS and anything besides PostgreSQL that you want to run on the machine. How much RAM is on the machine (or VM)? -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin