"g.bakalar...@icm.edu.pl" <g.bakalar...@icm.edu.pl> wrote: > Kevin Grittner <kgri...@ymail.com> wrote: >> "g.bakalar...@icm.edu.pl" <g.bakalar...@icm.edu.pl> wrote: >> >>> When doing these kind of statements >> >>> execute <unnamed>: CREATE TEMPORARY TABLE [...] >> >>> After few days [...] my huge server (192GB of RAM), gets stucked >>> due to no memory available (usually %commit is around 103-105%), >>> linux OOM killer goes into action - it usually kills one of >>> postgres processes - postmaster restart all databases) and after >>> all linux has again some 100GB of not commited memory >> >> What do you have as settings for temp_buffers and max_connections? >> > temp_buffers = 16GB > max_connections = 250
temp_buffers is per-connection, and any space allocated for this purpose by a connection is not released until the connection is closed. So you have configured your server to acquire and hold up to 3.9 TB of RAM for this purpose. http://www.postgresql.org/docs/current/static/runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-MEMORY > (with real number of connections about 120 and not going above) OK, so you can only get to 1.9 TB of RAM used for temp_buffers with 120 connections, but that's still way more than the 192 GB you actually have. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
