Hi,
There was a followup by the same author yesterday, where they add a
postgres backend for git (which at least addresses their "no indexes"
complaint). They give an example of a SQL query which cross-references a
Forgejo issue tracker with the commit log efficiently, which is
interesting. They mention at the end of the article that git's efficient
storage of diffs is a feature you would not get for free with a database.
https://nesbitt.io/2026/02/26/git-in-postgres.html
Something I did not see anybody else mention, and I am not completely
sure of my facts here, but doesn't guix's packaging model lean rather
heavily on packages being source code? More than other package
ecosystems, I mean. Since a guix package is a scheme object, which can
refer to data across modules, naively putting this text into a database
would not work. By comparison if your package registry is a bunch of
JSON files then it is straightforward to migrate that from git to a
database.
Dan
On 27/02/2026 14:55, Arun Isaac wrote:
Hi Ludo,
Thanks for chiming in! I'm pleased to hear that these issues are on the
radar. Just wanted to raise these points in case they weren't on the
radar. But, I feel reassured now. :-) We can hopefully work something
out.
Regards,
Arun
