3 ms·
Pretty sure Tom Lane said this will be a disaster in that same pgsql-hackers thread. Not entirely sure what benefits the multi-threaded model will have when you
by levkk 3y ago
Pretty sure Tom Lane said this will be a disaster in that same pgsql-hackers thread. Not entirely sure what benefits the multi-threaded model will have when you can easily saturate the entire CPU with just 128 connections and a pooler. So I doubt there is consensus or even strong desire from the community to undertake this boil the ocean project.
On the other hand, having the ability to shut down and cleanup the entire memory space of a single connection by just disconnecting is really nice, especially if you have extensions that do interesting things.
- BoardsOfCanada 3y agoFrom the article: > Tom Lane said: "I think this will be a disaster. There is far too much code that will get broken". He added later that the cost of this change would be "enormous", it would create "more than one security-grade bug", and that the benefits would not justify the cost.
- timcobb 3y agoYou can think of this as an opportunity to rewrite in Rust.
- tracker1 3y agoAfterPostgres
- krylon 3y agoMay I humbly suggest PostPostgres, or Post²gres?
- tomjakubowski 3y ago2Post2Furigres
- moi2388 3y agoPostgr3s: Tokyo Thread
- ilyt 3y ago>Not entirely sure what benefits the multi-threaded model will have when you can easily saturate the entire CPU with just 128 connections and a pooler. That the all of those would work faster because of performance benefits, as mentioned in article