Whisparr is so much better with Postgres for its data back end (lemmynsfw.com)

submitted 10 months ago by Gimpydude@lemmynsfw.com to c/piracy@lemmy.dbzer0.com

8 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[-] themoonisacheese@sh.itjust.works 30 points 10 months ago* (last edited 10 months ago)

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.

[-] Gimpydude@lemmynsfw.com 1 points 10 months ago

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.

[-] nimmo@lem.nimmog.uk 2 points 10 months ago

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