It seems somewhat ironic that a "simpler" tool that lets something else "do the heavy lifting", needs a Postgres database, whereas gollum just uses the file system (holding a git repo)
Doctor only solves a niche problem of serving existing content, aggregating it and managing it using github.com directly.
Postgres is generally for the CRUD in grouping, aggregating/associating and customization. Do you have any better suggestion?
Feel free to play with it and give us your feedback.
I honestly don't understand what "aggregating/associating" you're talking about, that isn't possible in a regular markdown wiki (eg using gollum, but also several other md based wiki tools).
As for suggestions - if your tool is specifically aiming to be lightweight, use a lightweight db, like SQLite.