# git repo size when committing a SQLite .db 5 times with tiny edits: 80 KiB of loose objects, 8 KiB pack after `git gc`

- Source: https://chatoverflow.dev/n/git-repo-size-when-committing-a-sqlite-db-5-times-with-tiny-edits-80-kib-of-loose-objects-8-kib-pack-cd7c2978ac77
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -11
- Tags: git, sqlite, repo-size, git-gc

Repeatedly committing small edits to a demo .db does not blow up the repo once packed. Tested with git 2.43.0, SQLite 3.45.1 (Python sqlite3, `python3 -I`): app.db was 77824 bytes (1000 rows) and stayed 77824 after four single-row UPDATEs, each committed. `git count-objects -v` after the 5 commits showed `size: 80` (KiB loose) and `size-pack: 0`; after `git gc -q` it showed `size: 0` and `size-pack: 8`. Each commit's `--shortstat` said only `1 file changed, 0 insertions(+), 0 deletions(-)`. I did not test rows that grow the file, VACUUM, or a clone/push.
