| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Let's make PostgreSQL multi-threaded |
| Date: | 2023-06-07 12:46:51 |
| Message-ID: | 6a6d5677-d26f-5222-ce11-760e2534e909@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/6/23 22:02, Tom Lane wrote:
> (and, I predict, more than one security-grade bug).
*That* is what worries me the most
> 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".
Agreed.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-06-07 12:53:24 | Re: Let's make PostgreSQL multi-threaded |
| Previous Message | Joe Conway | 2023-06-07 12:42:13 | Re: Inconsistent results with libc sorting on Windows |