| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | Rafia Sabih <rafia(dot)sabih(at)enterprisedb(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Effect of changing the value for PARALLEL_TUPLE_QUEUE_SIZE |
| Date: | 2017-05-31 14:52:08 |
| Message-ID: | CA+TgmoYCCp7_NUVOzKqA9hR-nz4YWZpkkVPJPs1a=BDg8tvLrQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 31, 2017 at 2:35 AM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> AFAIK, work_mem comes from memory private to the process whereas this
> memory will come from the shared memory pool.
I don't think that really matters. The point of limits like work_mem
is to avoid driving the machine into swap. Allocating shared memory
might error out rather than causing swapping in some cases on some
systems, but any difference between private and shared memory is not
the real issue here. The issue is overall memory consumption.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2017-05-31 14:53:22 | Re: Use of non-restart-safe storage by temp_tablespaces |
| Previous Message | Robert Haas | 2017-05-31 14:49:05 | Re: TAP backpatching policy |