Re:PostgreSQL reconsiders its process-based model
by carstenhag on Monday June 19, 2023 @03:43PM
(#36395673)
The person probably implied that Postgres should switch to another toolchain that guarantees more things at compile time, so probably Rust.
[ Parent
| on HN ]
Re:PostgreSQL reconsiders its process-based model
by blincoln on Monday June 19, 2023 @04:35PM
(#36396151)
If the existing code is old-school enough to use thousands of global variables in a thread-unsafe way, seems like changing it enough to compile as safe Rust code would push the "non-trivial" envelope pretty far.
Re:PostgreSQL reconsiders its process-based model
by bb88 on Monday June 19, 2023 @04:54PM
(#36396328)
You can take a chunk of code and just rewrite it in Rust. You'll learn a lot quickly by this.
Re:PostgreSQL reconsiders its process-based model
by tylerhou on Monday June 19, 2023 @05:22PM
(#36396653)
The boundaries within database code are not clear. There are too many interlocking parts to take a nontrivial chunk and rewrite it Rust.
Re:PostgreSQL reconsiders its process-based model
by steve_adams_86 on Monday June 19, 2023 @05:17PM
(#36396595)
It’s sort of like the inverse of the Matrix when Neo learns kung fu. You realize that you actually don’t know how to program :)