From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: how does PostgreSQL determine how many parallel processes to start |
Date: | 2021-02-19 10:21:51 |
Message-ID: | CAKoxK+75LgN40TBUNTBgWYfr8SYFNvPUJqe0cgDggzGUBw92fQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Feb 19, 2021 at 10:43 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> At execution time, PostgreSQL will use as many of the planned workers
> as are currently available (max_parallel_workers).
Thanks, but just to make it clear, assuming I execute almost
simultanously two identical queries that can be therefore be
parallelized, does that mean that the first one will be executed with
the max available parallele capacity and the second will "starve" on
parllelism being executed sequentially. Is this correct?
As a consequence to that, this also could mean that a query over a
small table could take more advanatge (in parallel sense) than a scan
on a larger table that was issued just a moment after (assuming both
table can be scanned in parallel), right?
Luca
From | Date | Subject | |
---|---|---|---|
Next Message | M Tarkeshwar Rao | 2021-02-19 10:51:32 | RE: Autovacuum not functioning for large tables but it is working for few other small tables. |
Previous Message | Laurenz Albe | 2021-02-19 09:43:17 | Re: how does PostgreSQL determine how many parallel processes to start |