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.
3014248210http://paper.people.com.cn/rmrb/pc/content/202602/27/content_30142482.htmlhttp://paper.people.com.cn/rmrb/pad/content/202602/27/content_30142482.html11921 十四届全国人大常委会第二十一次会议在京闭幕。下载安装 谷歌浏览器 开启极速安全的 上网之旅。是该领域的重要参考
更多详细新闻请浏览新京报网 www.bjnews.com.cn。Safew下载是该领域的重要参考
[&:first-child]:overflow-hidden [&:first-child]:max-h-full"