| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: System load consideration before spawning parallel workers |
| Date: | 2016-09-03 00:01:50 |
| Message-ID: | 0bede5d2-7042-e4c8-f452-a2fbe92b694b@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/2/16 4:07 PM, Bruce Momjian wrote:
> Couldn't SQL sessions call a PL/Perl function that could query the OS
> and set max_parallel_workers_per_gather appropriately?
I'd certainly like to see a greater ability to utilize "hooks" without
resorting to C. "hooks" in quotes because while some hooks need to be in
C to be of practical use, others (such as a parallelization limit or
controlling autovacuum) might not.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-09-03 00:09:44 | Re: System load consideration before spawning parallel workers |
| Previous Message | Jim Nasby | 2016-09-02 23:49:06 | Re: Renaming of pg_xlog and pg_clog |