From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Prasad <prasadnine(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: RAM usage of PostgreSql |
Date: | 2019-04-04 17:46:30 |
Message-ID: | 20190404174630.GE17544@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice pgsql-performance |
Hi,
|Cc: pgsql-novice(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org
Please don't cross post to multiple lists.
On Thu, Apr 04, 2019 at 08:18:01PM +0530, Prasad wrote:
> There are lot of allocations in postgresql.conf file, for example
> shared_buffers, work_mem...etc.
>
> As per my knowledge, all postgres processes should not consume the RAM more
> than the value assigned in shared_buffers.Please clarify and let me know if
> I misunderstand the concept..
shared_buffers is what's *reserved* for postgres and unavailable for other
processes whenever PG is running.
work_mem is what each postgres process might use, if needed. When complete,
that's returned to the OS. Note that an expensive query might actually use
some multiple of work_mem (it's per sort/hash node and also per parallel
process, and also hash aggregate can sometimes use more than work_mem).
Justin
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2019-04-04 18:08:05 | Re: RAM usage of PostgreSql |
Previous Message | Prasad | 2019-04-04 14:48:01 | RAM usage of PostgreSql |
From | Date | Subject | |
---|---|---|---|
Next Message | Rijo Roy | 2019-04-04 18:03:44 | Re: monitoring options for postgresql under AWS/RDS? |
Previous Message | Justin Pryzby | 2019-04-04 17:43:22 | Re: monitoring options for postgresql under AWS/RDS? |