Parallel threads in query - Mailing list pgsql-hackers

From Darafei "Komяpa" Praliaskouski
Subject Parallel threads in query
Date
Msg-id CAC8Q8tKNO3pQguAEL8mXw8RdUMZ95T+BwTEozybOqTPKConEiA@mail.gmail.com
Whole thread Raw
Responses Re: Parallel threads in query  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Parallel threads in query  (David Fetter <david@fetter.org>)
Re: Parallel threads in query  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
List pgsql-hackers
Hi,

I've tried porting some of PostGIS algorithms to utilize multiple cores via OpenMP to return faster.

Question is, what's the best policy to allocate cores so we can play nice with rest of postgres?

What I'd like to see is some function that I can call and get a number of threads I'm allowed to run, that will also advise rest of postgres to not use them, and a function to return the cores back (or do it automatically at the end of query). Is there an infrastructure for that?
--
Darafei Praliaskouski
Support me: http://patreon.com/komzpa

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Super PathKeys (Allowing sort order through precision loss functions)
Next
From: David Rowley
Date:
Subject: Re: Super PathKeys (Allowing sort order through precision loss functions)