Dhruv Shukla <dhruvshukla82@xxxxxxxxx> wrote: > Other informational details about configurations are: > shared_buffers = 80GB > temp_buffers = 2GB > work_mem = 2GB > maintenance_work_mem = 16GB Well, at the default max_connections of 100 that could easily result in the server trying to allocate about 567GB of RAM. If your number of connections is more than 100, adjust proportionally higher. If the server doesn't have that, you could see extreme swapping or various other problems as the OS tries to survive. > effective_cache_size = 130GB And the planner will be generating plans based on the assumption that the combination of shared_buffers and the OS cache will have this much RAM available for caching, so if you have max_connections = 100 this configuration would only make sense on a machine with RAM of 617GB or more, plus whatever is needed for the OS and anything besides PostgreSQL that you want to run on the machine. How much RAM is on the machine (or VM)? -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
