If you understand Postgres's problems so well (though in reality, such problems can occur in many applications, and it's unclear how your rewritten version attempts to solve them), then why not address them in the main branch by becoming a contributor.
Less code and more value.
If you understand Postgres's problems so well (though in reality, such problems can occur in many applications, and it's unclear how your rewritten version attempts to solve them), then why not address them in the main branch by becoming a contributor. Less code and more value.
It is explained in the article: Any of those changes require massive or incompatible changes.
So they want 100% compatibility first and then implement features that require massive and incompatible changes?
Checks out, pgrust is mainly an LLM driven rewrite with minimum supervision and guided by 100% test suite conformance.
No, this note is another declaration without exact explanation. If you have real bugs you should send a bug report, that's all.
Maybe you should start from bug report without LLM-slop?