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.
@renchap@thisismissem@hrefna@Gargron Not really. DB migrations put aside, the main thing the application has to do is to add the partition key into the where clause to ensure performances stay good.
e.g. if you partition table toot by user_id, you have to run something like SELECT message FROM toots WHERE toot_id = foo AND user_id = bar.
This prevents the query planner from scanning all the sub tables.
@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.
