Postgres has its own primitives for things that forges currently build custom infrastructure around. A trigger on the refs table firing NOTIFY means any connected client learns about a push the moment it happens, which is how forges normally end up building a custom webhook polling layer. Multi-tenant repo isolation becomes a database concern through row-level security on the objects and refs tables, and logical replication lets you selectively stream repositories across Postgres instances, a kind of partial mirroring that filesystem-based git can’t do. Commit graph traversal for ancestry queries and merge-base computation falls to recursive CTEs, and pg_trgm indexes on blob content give you substring search across all repositories without standing up a separate search index.
Что думаешь? Оцени!
，更多细节参见新收录的资料
Switching to multi-thread, the number of physical cores per vCPU makes the difference:
{\renewcommand{\arraystretch}{1.5}\begin{bmatrix}
6ZustandStrong DefaultState Management