Re: proposal: Allocate work_mem From Pool

From: Joseph D Wagner <joe(at)josephdwagner(dot)info>
To: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: proposal: Allocate work_mem From Pool
Date: 2022-07-13 03:49:10
Message-ID: 1ac57119a27c557743bd5f3e24c0ef1c@josephdwagner.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> Before I try to answer that, I need to know how the scheduler works.

> As I understand the term used, there is no scheduler inside Postgres
> for user connections -- they're handled by the OS kernel.

Then, I'm probably using the wrong term. Right now, I have
max_worker_processes set to 16. What happens when query #17
wants some work done? What do you call the thing that handles
that? What is its algorithm for allocating work to the processes?
Or am I completely misunderstanding the role worker processes
play in execution?

Joseph Wagner

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2022-07-13 04:05:54 Re: making relfilenodes 56 bits
Previous Message David Rowley 2022-07-13 03:37:19 Re: POC: GROUP BY optimization