Memory usage of PostgreSQL
shared_buffers are statically taken at startup and are never resized.
effective_cache_size is just a hint to the optimizer. it is never allocated. it merely gives a hint of what is going on. so shared_buffers is what you see as taken.