Re: [PERFORM] Connections "Startup"

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

Re: [ADMIN] [PERFORM] Connections "Startup"

Postgres is designed in this way. It can handle such problem by adopting the following steps: 1.Increase the kernal level parameters:shmmax and shmallexample for 2GB RAM size for postgres processing is below vi /etc/sysctl.confkernel.shmmax = 2147483648 kernel.shmall = 2883584 similar way you

Re: [PERFORM] Connections "Startup"

Hi 2015-12-22 8:59 GMT+01:00 Artem Tomyuk : > Hi. > > I've noticed huge decrease in performance. > During this in htop i see a lot (200 - 300) of connections in state > "startup", each of them eats 3-3% of CPU time. This processes are not > visible in pg_stat_activity so i

[PERFORM] Connections "Startup"

Hi. I've noticed huge decrease in performance. During this in htop i see a lot (200 - 300) of connections in state "startup", each of them eats 3-3% of CPU time. This processes are not visible in pg_stat_activity so i cant understand what they are doing, and i cant kill them. I cant see the

Re: [PERFORM] Connections "Startup"

You can definitely overload most systems by trying to start too many connections at once. (This is actually true for most relational databases.) We used to see this scenario when we'd start a bunch web servers that used preforked apache at the same time (where each fork had its own connection).

Re: [ADMIN] [PERFORM] Connections "Startup"

2015-12-23 4:52 GMT+01:00 Om Prakash Jaiswal : > > *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 >