Answer the question
In order to leave comments, you need to log in
Why doesn't PostgreSQL eat more memory?
Good day to all!
I have an instance specially for PostgreSQL raised .. but he does not want to eat more (the total memory is occupied about 6%, this is with OS).
The config is as follows:
max_connections = 200
shared_buffers = 2GB
effective_cache_size = 5GB
work_mem = 10MB
maintenance_work_mem = 448MB
min_wal_size = 1GB
max_wal_size = 2GB
checkpoint_completion_target = 0.7
wal_buffers = 16MB
default_statistics_target = 100
RAM: 8GB
PS
SHOW ALL - shows modified data config loads fine
Answer the question
In order to leave comments, you need to log in
Apparently he doesn't need more.
How big is the table, how many queries, how complex?
See EXPLAIN (ANALYZE,BUFFERS)
Well, shared_buffers can be raised up to 4-6 GB.
Here is an important point, what kind of database do you have and how is it currently used.
Those. if the application used by this database is a simple accounting system with a minimum of functionality that is visited once a quarter, then everything is ok. If the application is more complicated and is used often, and there are quite a few people working there in parallel, then, most likely, everything is also ok, but here I would advise you to install a DBA beer that worked with requests and would suggest that it continue in the same spirit.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question