3 ms·
The person probably implied that Postgres should switch to another toolchain that guarantees more things at compile time, so probably Rust.
by carstenhag 3y ago
The person probably implied that Postgres should switch to another toolchain that guarantees more things at compile time, so probably Rust.
- blincoln 3y agoIf 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.
- bb88 3y agoYou can take a chunk of code and just rewrite it in Rust. You'll learn a lot quickly by this.
- steve_adams_86 3y agoIt’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 :)
- tylerhou 3y agoThe boundaries within database code are not clear. There are too many interlocking parts to take a nontrivial chunk and rewrite it Rust.