PostgreSQL reconsiders its process-based model
1–10 of 377 posts
Re: PostgreSQL reconsiders its process-based model
#2I'm honestly surprised it took them so long to reach this conclusion.
> That idea quickly loses its appeal, though, when one considers trying to create and maintain a 2,000-member structure, so the project is unlikely to go this way.
As repulsive as this might sound at first, I've seen structures of hundreds of fields work fine if the hierarchy inside them is well organized and they're not just flat. Still, I have no real knowledge of the complexity of the code and wish the Postgres devs all the luck in the world to get this working smoothly.
Re: PostgreSQL reconsiders its process-based model
#3Some interesting discussion on this here also: https://news.ycombinator.com/item?id=36284487
Re: PostgreSQL reconsiders its process-based model
#4This would be one those places where a language like Rust would be helpful. In C/C++ with undefined behavior and crashes, process isolation makes a lot of sense to limit the blast radius. Rust borrow checker gives you at compile time a lot of the safety that you would rely on process isolation for.
Re: PostgreSQL reconsiders its process-based model
#5That sounds like really hard programming. I’m glad I write react and get paid possibly much more.
Re: PostgreSQL reconsiders its process-based model
#6Changing something so fundamental seems like it should be a rewrite.
Re: PostgreSQL reconsiders its process-based model
#7I'm honestly surprised it took them so long to reach this conclusion. > That idea quickly loses its appeal, though, when one considers trying to create and maintain a 2,000-member structure, so the project is unlikely to go this way. As repulsive as this might sound at first, I've seen structures of hundreds of fields work fine if the hierarchy inside them is well organized and they're not just flat. Still, I have no…
Yeah. I think as a straightforward, easily correct transition from 2000 globals, a giant structure isn't an awful idea. It's not like the globals were organized before! You're just making the ambient state (awful as it is) explicit.
Re: PostgreSQL reconsiders its process-based model
#8I hope they are conservative about this, because even the smartest and best programmers in the world cannot create bug free multithreaded code.
Re: PostgreSQL reconsiders its process-based model
#9This sounds like a problem that would border on the complexity of replacing the GIL in Ruby or Python. The performance benefits are obvious but it seems like the correctness problems would be myriad and a constant source of (unpleasant) surprises.
Re: PostgreSQL reconsiders its process-based model
#10I hope they are conservative about this, because even the smartest and best programmers in the world cannot create bug free multithreaded code.
The fact that they are planning on doing this across multiple releases gives me hope that they'll be cautious with this.