Whisparr is so much better with Postgres for its data back end
Whisparr is so much better with Postgres for its data back end
I have a library of videos that I've downloaded with whisparr running in a docker container. I've had a problem with the sqlite DB getting corrupted on a daily basis. I followed the guide on switching to postgres and it only took about 15 minutes, including setting up a postgres server. I really recommend anyone running it to do that. There's been a noticeable performance boost too.
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.
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 the same experience with some of the 'arr projects.
Interesting, I didn't know you could migrate the other 'arr projects to postgres. Definitely gonna attempt this later tonight.
I'm going to move my others to postgres as well. It's dead simple and so much better.
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
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.