Spent some time on my #ActivityPub project today getting #PSQL set up. There's a lot of random setup that goes into PSQL and it isn't especially well documented (or rather, it is so well documented there is simply too much of it).
Whether I stick with it is a separate question. Comparing it to the other options and including the learning curve it is head and shoulders the best pick for me for right now, however, at least for a production-level database.
@Arcaik@renchap@thisismissem@hrefna Uniqueness constraints are not asserted across partitions so it requires a bit more awareness at the application layer. Our code also has to work for all installs and not just ones with DevOps engineers.
@Gargron@renchap@thisismissem@hrefna What I'm saying is that one could make Mastodon “partitioning ready” with a few changes and let people who know what they are doing implement it if they need it.
How I am prototyping playing around with #ActivityPub this time (with bonus #OCaml) for databases:
Basically I'm building a thin shim over the database API layer. This is both remarkably easy and remarkably weird in OCaml, so it makes for a good learning experience and gets me a little more comfortable with modules.
The first pass I'm just writing the basics with #sqlite3, later I'll go through and modify it to work with #PSQL and/or other options.