Git packfiles use delta compression, storing only the diff when a 10MB file changes by one line, while the objects table stores each version in full. A file modified 100 times takes about 1GB in Postgres versus maybe 50MB in a packfile. Postgres does TOAST and compress large values, but that’s compressing individual objects in isolation, not delta-compressing across versions the way packfiles do, so the storage overhead is real. A delta-compression layer that periodically repacks objects within Postgres, or offloads large blobs to S3 the way LFS does, is a natural next step. For most repositories it still won’t matter since the median repo is small and disk is cheap, and GitHub’s Spokes system made a similar trade-off years ago, storing three full uncompressed copies of every repository across data centres because redundancy and operational simplicity beat storage efficiency even at hundreds of exabytes.
Что думаешь? Оцени!
。业内人士推荐同城约会作为进阶阅读
「該怎麼說呢？在奧運贏得獎牌對每位運動員而言都是改變人生的經歷。五度奪牌的難度更是呈指數級增長——每面獎牌對我而言同樣艱辛，但外界的期待值卻不斷攀升，對吧？」
[&:first-child]:overflow-hidden [&:first-child]:max-h-full"