| From: | Sebastian Dressler <sebastian(at)swarm64(dot)com> |
|---|---|
| To: | Sujith Kumar(dot)S <sujiplr(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: CPU Configuration - postgres |
| Date: | 2020-06-11 13:53:37 |
| Message-ID: | 16DB7D72-AA9D-451F-9C2D-B39A03021EB6@swarm64.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
> On 11. Jun 2020, at 10:24, Sujith Kumar.S <sujiplr(at)gmail(dot)com> wrote:
>
> Is there any configuration in postgresql that restrict the number of CPU usage by postgres process.
For parallelism, there are these options:
- max_parallel_workers_per_gather
- max_parallel_workers
- max_worker_processes
Where the first two essentially can limit the amount of cores to be used.
Is that what you were asking for?
Cheers,
Sebastian
--
Sebastian Dressler, Solution Architect
+49 30 994 0496 72 | sebastian(at)swarm64(dot)com
Swarm64 AS
Parkveien 41 B | 0258 Oslo | Norway
Registered at Brønnøysundregistrene in Norway under Org.-Number 911 662 787
CEO/Geschäftsführer (Daglig Leder): Thomas Richter; Chairman/Vorsitzender (Styrets Leder): Dr. Sverre Munck
Swarm64 AS Zweigstelle Hive
Ullsteinstr. 120 | 12109 Berlin | Germany
Registered at Amtsgericht Charlottenburg - HRB 154382 B
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Brusselback | 2020-06-11 14:36:50 | Re: CPU Configuration - postgres |
| Previous Message | Adrian Klaver | 2020-06-11 13:47:50 | Re: pgbouncer logrotate found error, skipping |