Мерц резко сменил риторику во время встречи в Китае09:25
19:28, 27 февраля 2026Экономика
，详情可参考服务器推荐
17. 理论动态| 坚持稳中求进、提质增效努力实现“十五五”良好开局————理论学习, www.ccdi.gov.cn/llxx/202602…
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.
Get Deal at Amazon