Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aBaW2-00037u-VI for pgsql-admin@arkaria.postgresql.org; Wed, 23 Dec 2015 03:55:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aBaW2-0007S8-Bj for pgsql-admin@arkaria.postgresql.org; Wed, 23 Dec 2015 03:55:06 +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) (envelope-from ) id 1aBaW1-0007Rz-Ml for pgsql-admin@postgresql.org; Wed, 23 Dec 2015 03:55:05 +0000 Received: from nm31-vm6.bullet.mail.gq1.yahoo.com ([98.136.216.213]) by makus.postgresql.org with esmtps (TLS1.0:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aBaVy-0004G1-AE for pgsql-admin@postgresql.org; Wed, 23 Dec 2015 03:55:04 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.in; s=s2048; t=1450842898; bh=Ot3+U4DgzeSuHpKS8hIFnnMY2ELx3kAsbfatCe8cnCA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=rn4/S3k8JD946ydXScQ9ykA3lL/qzakAQ0NyBwbyS8DvNqyMt/sKJi17Ck4VYVieBE4+kux2cWBTWoMvYd4+MUp7zB/mrhAsxoTfv/Ys4eCF9muFZ6bzwtTbL0c36bezMifQKW7s7ww/zADgP7dKxEkbCWn+w58gXRgLOzwTGJ0tCvBSa6pBKiaklQOMPhyYeq8TxWYV/3fz4vlD/WAi+fW8BnsdQJLfPIBbcwR12r5NgOHl6ZGvAyQ1GKAneifAps0ydjGwxGEkP1ojTOtXtGXQD6zm2er5Yu2besQqMzZuE34hZQqvYJdtIs8rXAv4KMnY2xNgd5B29sLKcOnxKw== Received: from [127.0.0.1] by nm31.bullet.mail.gq1.yahoo.com with NNFMP; 23 Dec 2015 03:54:58 -0000 Received: from [98.137.12.57] by nm31.bullet.mail.gq1.yahoo.com with NNFMP; 23 Dec 2015 03:52:10 -0000 Received: from [106.10.166.116] by tm2.bullet.mail.gq1.yahoo.com with NNFMP; 23 Dec 2015 03:52:09 -0000 Received: from [106.10.151.219] by tm5.bullet.mail.sg3.yahoo.com with NNFMP; 23 Dec 2015 03:52:09 -0000 Received: from [127.0.0.1] by omp1017.mail.sg3.yahoo.com with NNFMP; 23 Dec 2015 03:52:09 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 293376.59312.bm@omp1017.mail.sg3.yahoo.com X-YMail-OSG: CeEGjjAVM1ld6j.N8Oc1BglUxMnkJHjl5vbLGBhuoK.yfEoQfPpdrRwTmDIp99p 1FmRe3Ru.JRN1jMKboty1rlHngoi_Xwqgd9pNOGIlncuQDNb3zPgKx9kQ3TDMLaDDfUqmuKopMMs 5CQcKq3D5CfIj1HmbJvbCscP0FbYNLQ4aQd8c8emNvg7SSl7fIbPgicP78JV5TqAeZ5Fow8hYbGo MNou2GLkbRzN7Aun7N8n50XycZEmKHG92bZGbuJQ2ue927hS6xpwQXVIUA8A9AgSO4Vo.Li2Zedn eQXoCn8Nu8pSoBax5r9bAhRHDQlef8WTWSv9IzXQRjQJrg3mQvxUBadW0GORYk4SU0Cwf3e16hag Tf4_bhousHqcaxqo7MdMuRTa5NhodJ1JRqc7P.U0fKdLlZFy.ThcgGUPgwYJoFlsObKCuTfP42iw O0nC_NjkSoJCvVwh5xX2eSNkzmwyJwvBfCHd6baYU1SRUkBhdxn5.K9jjZ2MeiIbLqnf0fhVaWFz 8sV7nnhktuPMcCAaKV6KHHOjc Received: by 106.10.196.88; Wed, 23 Dec 2015 03:52:08 +0000 Date: Wed, 23 Dec 2015 03:52:08 +0000 (UTC) From: Om Prakash Jaiswal Reply-To: Om Prakash Jaiswal To: Jim Nasby , Pavel Stehule , Artem Tomyuk Cc: "pgsql-performance@postgresql.org" , pgsql-admin Message-ID: <714748102.2375398.1450842728534.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <567A07D9.7060401@BlueTreble.com> References: <567A07D9.7060401@BlueTreble.com> Subject: Re: [PERFORM] Connections "Startup" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2375397_2139595096.1450842728527" Content-Length: 5265 X-Pg-Spam-Score: -2.7 (--) 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 ------=_Part_2375397_2139595096.1450842728527 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Postgres is designed in this way. It can handle such problem by adopting th= e following steps:=20 1.Increase the kernal level parameters:shmmax and shmallexample for 2GB RAM= size for postgres processing is below vi /etc/sysctl.confkernel.shmmax =3D 2147483648 kernel.shmall =3D 2883584 similar way you increase the configuration paramater for half of RAM size o= f your machine. 2. Edit your postgresql.conf file following settings: a. Increase the number of connection parameter. =C2=A0Connection =3D 500 b.Effective_cache_size =3D 2GB c. Shared_memory =3D 500MB =C2=A0 =20 =20 On Wednesday, 23 December 2015 8:04 AM, Jim Nasby wrote: =20 On 12/22/15 2:09 AM, Pavel Stehule wrote: > > There was lot of bugfix releases after 9.1.2 - currently there is > PostgreSQL 9.2.19. I'm sure Pavel meant 9.1.19, not 9.2.19. In any case, be aware that 9.1 goes end of life next year. You should=20 start planning on a major version upgrade now if you haven't already.=20 9.5 should release in January so you might want to wait for that version. --=20 Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin ------=_Part_2375397_2139595096.1450842728527 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 
Postgres i=
s designed in this way. It can handle such problem by adopting the followin=
g steps:
1.I= ncrease the kernal level parameters:
shmmax and shmall
example for 2GB RAM size for postgres processing= is below
<=
strong class=3D"" id=3D"yui_3_16_0_1_1450839346074_4478">vi /etc/sysctl.con=
f
kern=
el.shmmax =3D 2147483648
kernel.shmall =3D 2883584

similar way yo=
u increase the configuration paramater for half of RAM size of your machine=
.

2. Edit your postgresql.conf file following settings:
a. Increa=
se the number of connection parameter.
 Connection =3D 500
b.Eff=
ective_cache_size =3D 2GB
c. Shared_memory =3D 500MB


 



<= font face=3D"Arial" size=3D"2"> On Wednesday, 23 December 2015 8:04 AM, Jim= Nasby <Jim.Nasby@BlueTreble.com> wrote:


<= div class=3D"y_msg_container">On 12/22/15 2:09 AM, Pavel Stehule wrote:
>
> There was lot of bugfix releases after 9.1.2 - currently the= re is
> PostgreSQL 9.2.19.

I'm sure Pavel meant 9.1.19, not 9.2.19.
=
In any case, be aware that 9.1 goes end of life next yea= r. You should
start planning on a major version upgrade = now if you haven't already.
9.5 should release in Januar= y so you might want to wait for that version.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com


--
Sent = via pgsql-admin mailing list (pgsql-admin@p= ostgresql.org)
To make changes to your subscription:<= br clear=3D"none">http://www.postgresql.org/mailpref/pgsql= -admin



------=_Part_2375397_2139595096.1450842728527--