The person probably implied that Postgres should switch to another toolchain that guarantees more things at compile time, so probably Rust.

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.

The boundaries within database code are not clear. There are too many interlocking parts to take a nontrivial chunk and rewrite it Rust.

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 :)

Microsoft SQL Server has SQLOS which is another way [0].

[0] https://www.thegeekdiary.com/what-is-sql-server-operating-sy...

I think it's meant to imply the solution given in their username ("idiomatic Rust").

> I think it's meant to imply the solution given in their username ("idiomatic Rust").

I think "Idiom: a tic (Rust)" can also fit if I squint hard enough and decide it looks like a definition from an online dictionary :-)

Don’t mind the gimmick gallery (username).