Postgres in general is a considerably better db engine than SQLite in every metric except portability. Whenever you need more than a simple config storage, I heavily recommend using postgres. If it's good enough for gitlab, it's good enough for me.
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
I totally agree. I've been using it on and off since the 90's but I've never known that you can use it with the *arr apps.
I think it's a relatively recent thing. As the documentation for each of the *arts has a relatively recent minimum version number I think.
Here's where I went when looking for whisparr, but just replace that with the arr you're wanting to use and it'll give you decent steps for getting your database created and migrated into it: https://wiki.servarr.com/whisparr/postgres-setup
I had trouble with the sqlite databases when I was writing them to a remote volume over nfs. I've had zero issues since moving them to local disk and performance is great.
Just set up my arr apps to use rdtc on a 500gb VirtualBox Linux machine and I love it, I'll keep this in mind when adding whisparr ty