Мощный удар Израиля по Ирану попал на видео09:41
战略节奏再聚焦与创始人回归掌舵Workday股价的急剧下跌反映出投资者对AI如何颠覆传统软件公司的焦虑与日俱增。
。91视频对此有专业解读
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.
Option 2: For very localized changes, it might even re-evaluate all shortcuts within that one affected cluster.
Leave a comment on blogs or forums.