Search Postgresql Archives

Re: Kernel kills postgres process - help need

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



=?utf-8?q?Herv=C3=A9_Piedvache?= <bill.footcow@xxxxxxxxx> writes:
> When I have a lot of connexions (persistante connexions from 6 web apache/php 
> serveurs using PDO, about 110 process on each web servers) on the server, or 
> long request, it's difficult for me to know when it's appening, the kernel 
> seems to kill my postgresql process then the server become completly 
> instable, and most of the time need a reboot ...

Turn off memory overcommit.

> max_connections = 2048

Have you considered using a connection pooler in front of a smaller
number of backends?

If you really need that many backends, it'd likely be a good idea to
reduce max_files_per_process to perhaps 100 or so.  If you manage
to run the kernel out of filetable slots, all sorts of userland stuff
is going to get very unhappy.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux