Repository navigation
feature request: optional postgresql as storage instead of sqlite #26
Description
Hey there! First of all: nice project! :)
I see that one of the main core feature of the project is to not have a database. Since I am deploying this in a Kubernetes environment, I need to provide a persistent volume to the pod, just for a sqlite. Knowing how sqlite and my storage solution works, not having a database makes it less of a "good feature" when deploying.
I noticed though that it uses a sqlite DB, and my pervious analytics tool (umami) was using postgresql. This allowed me to scale with multiple instances for redundancy in case some of the nodes in my homelab would need repair.
It would be awesome if Liwan would also support postgresql and act as a stateless application :)
Thank you again for the project! It looks super nice 👍
Reacted by Abdessamad, Pyvonix, Intestinall and satonotdead
Activity
[-]feature: postgresql[/-][+]feature request: optional postgresql as storage instead of sqlite[/+]explodingcamera commentedon Aug 5, 2026
Closing this in favor of #44
koalalorenzo commentedon Aug 5, 2026
@explodingcamera the issue was not to move to duckdb but to postresql. :D I don't think it duplicates #44 but if that is the direction it makes sense to pick it.
explodingcamera commentedon Aug 5, 2026
Hi, as part of adding support for remote duckdb servers (so liwan can run stateless) I also want to try out using duckdb's postgres extension / maybe also pg_duckdb to see if that's a possibility. Performance didn't look that great from benchmarks posted by duckdb though so I'll have to see.