Re: Parallel threads in query
| От | Paul Ramsey |
|---|---|
| Тема | Re: Parallel threads in query |
| Дата | |
| Msg-id | CACowWR0n_2G2ta6Edn6LSYZSXgVD_N6aiJEBaROnWVc_8mABbA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Parallel threads in query (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Parallel threads in query
|
| Список | pgsql-hackers |
On Wed, Oct 31, 2018 at 2:11 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Darafei "Komяpa" Praliaskouski <me@komzpa.net> writes:
> Question is, what's the best policy to allocate cores so we can play nice
> with rest of postgres?
There is not, because we do not use or support multiple threads inside
a Postgres backend, and have no intention of doing so any time soon.
As a practical matter though, if we're multi-threading a heavy PostGIS function, presumably simply grabbing *every* core is not a recommended or friendly practice. My finger-in-the-wind guess would be that the value of max_parallel_workers_per_gather would be the most reasonable value to use to limit the number of cores a parallel PostGIS function should use. Does that make sense?
P
В списке pgsql-hackers по дате отправления: