2015-12-23 4:52 GMT+01:00 Om Prakash Jaiswal <op1...@yahoo.co.in>: > > *Postgres is designed in this way. It can handle such problem by adopting the > following steps: * > > 1.Increase the kernal level parameters: > shmmax and shmall > example for 2GB RAM size for postgres processing is below > > *vi /etc/sysctl.conf* > > kernel.shmmax = 2147483648 > kernel.shmall = 2883584 > > similar way you increase the configuration paramater for half of RAM size of > your machine. > > 2. Edit your postgresql.conf file following settings: > a. Increase the number of connection parameter. > Connection = 500 > b.Effective_cache_size = 2GB > c. Shared_memory = 500MB > > increasing max connection when you have these strange issues isn't good advice. Running 500 connections on 2GB server is highly risky.
Pavel > > > > > > > > On Wednesday, 23 December 2015 8:04 AM, Jim Nasby <jim.na...@bluetreble.com> > wrote: > > > 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 > start planning on a major version upgrade now if you haven't already. > 9.5 should release in January 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 > <http://bluetreble.com/> > > > -- > Sent via pgsql-admin mailing list (pgsql-ad...@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > > > >
