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.
l00777 0 0 0 /lib64 - usr/lib64
。关于这个话题，Line官方版本下载提供了深入分析
The Hunt for Dark Breakfast，推荐阅读服务器推荐获取更多信息
各地区各部门各单位教育引导党员干部深入学习习近平总书记关于树立和践行正确政绩观的重要论述，深入学习《中共中央关于制定国民经济和社会发展第十五个五年规划的建议》，深入学习习近平总书记关于本地区本部门本领域的重要讲话和重要指示精神，推动学习教育走深走实。。关于这个话题，51吃瓜提供了深入分析