| From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
|---|---|
| To: | Joseph D Wagner <joe(at)josephdwagner(dot)info> |
| 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-12 12:31:56 |
| Message-ID: | CAFBsxsH9KF8_9H5aczTPh5hFt4Leat_Xcnw=cqaiazwwzV_qwQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 12, 2022 at 5:55 PM Joseph D Wagner <joe(at)josephdwagner(dot)info>
wrote:
> 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. That's probably why
it'd be a difficult project to be smart about memory -- step one might be
to invent a scheduler. (The autovacuum launcher and checkpointer, etc have
their own logic about when to do things, but while running they too are
just OS processes scheduled by the kernel.)
--
John Naylor
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Drouvot, Bertrand | 2022-07-12 12:58:27 | Re: Patch proposal: New hooks in the connection path |
| Previous Message | Amit Kapila | 2022-07-12 12:24:59 | Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication |