From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Jeremy Schneider <schneider(at)ardentperf(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Thomas Kellerer <shammat(at)gmx(dot)net>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Let's make PostgreSQL multi-threaded |
Date: | 2023-06-10 00:23:08 |
Message-ID: | ZIPCbJaeNHvPTpBe@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 8, 2023 at 11:37:00AM +1200, Thomas Munro wrote:
> It's old, but this describes the 4 main models and which well known
> RDBMSes use them in section 2.3:
>
> https://dsf.berkeley.edu/papers/fntdb07-architecture.pdf
>
> TL;DR DB2 is the winner, it can do process-per-connection,
> thread-per-connection, process-pool or thread-pool.
>
> I understand this thread to be about thread-per-connection (= backend,
> session, socket) for now.
I am quite confused that few people seem to care about which model,
processes or threads, is better for Oracle, and how having both methods
available can be a reasonable solution to maintain. Someone suggested
they abstracted the differences so the maintenance burden was minor, but
that seems very hard to me.
Did these vendors start with processes, add threads, and then find that
threads had downsides so they had to keep both?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2023-06-10 00:37:57 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
Previous Message | Bruce Momjian | 2023-06-09 23:55:16 | Re: Let's make PostgreSQL multi-threaded |