1. License resistance
“AGPL is a dealbreaker.” – application
“AGPL is untested in courts … too dangerous.” – xyzzy_plugh
Many commenters cite the AGPL as a barrier to corporate adoption, warning that it “will never see wide adoption” and is “banned at Google and most sane companies.”
2. Verification & trust in performance claims
“We’ve been able to prove over 1,000 user‑facing functions have the exact same logic in both pgrust and Postgres.” – malisper
The maintainer emphasizes extensive testing—formal verification, differential fuzzing, and bug discovery—to build confidence in the project’s correctness and claimed 300× speedups.
3. Curiosity about performance & architecture
“If it is indeed 300 faster, I’m sure more rational corporations will rethink their license policy.” – guenthert
“pgrust seems to have good momentum.” – cognitiveinline*
Readers are intrigued by the technical details—scheduler design, columnar storage, and benchmark comparisons—asking for deeper architectural insight and real‑world use cases.