Re: Let's make PostgreSQL multi-threaded

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Let's make PostgreSQL multi-threaded
Дата
Msg-id 268998.1686103322@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Let's make PostgreSQL multi-threaded  (Thomas Munro <thomas.munro@gmail.com>)
Ответы Re: Let's make PostgreSQL multi-threaded  (Dilip Kumar <dilipbalaut@gmail.com>)
Re: Let's make PostgreSQL multi-threaded  (Joe Conway <mail@joeconway.com>)
Re: Let's make PostgreSQL multi-threaded  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Thomas Munro <thomas.munro@gmail.com> writes:
> ... My point is
> that we’re doing pretty unreasonable and inefficient contortions to
> develop new features -- we're not just happily chugging along without
> threads at no cost.

Sure, but it's not like chugging along *with* threads would be no-cost.
Others have already pointed out the permanent downsides of that, such
as loss of isolation between sessions leading to debugging headaches
(and, I predict, more than one security-grade bug).

I agree that if we were building this system from scratch today,
we'd probably choose thread-per-session not process-per-session.
But the costs of getting to that from where we are will be enormous.
I seriously doubt that the net benefits could justify that work,
no matter how long you want to look forward.  It's not really
significantly different from "let's rewrite the server in
C++/Rust/$latest_hotness".

            regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Julien Rouhaud
Дата:
Сообщение: Re: [PATCH] pg_regress.c: Fix "make check" on Mac OS X: Pass DYLD_LIBRARY_PATH
Следующее
От: "蔡梦娟(玊于)"
Дата:
Сообщение: 回复:回复:Fix missing initialization of delayChkptEnd