5 ms·
I feel like there are a lot of use cases where I’d opt for SQLite and a lot of use cases where I’d opt for Postgres + PgBouncer. I’m curious what kinds of featu
by ummonk 1mo ago
I feel like there are a lot of use cases where I’d opt for SQLite and a lot of use cases where I’d opt for Postgres + PgBouncer. I’m curious what kinds of features push towards using Postgres alone over SQLite.
- tyre 1mo agoAll of my personal apps use Postgres because: - types are lovely. We love types. SQLite’s default of non-strict typing is, to me, bananas. - SELECT DISTINCT ON is my ride-or-die - most importantly, I’m very comfortable in Postgres and the setup cost is basically zero (like SQLite) because Claude does it.
- panzi 1mo agoThe setup cost is basically zero anyway. Add apt repo, apt-get install the correct version. Easy to run different versions at the same time too. Upgrading is annoying.
- pocksuppet 1mo agoConcurrency, data types, scalability, centralization, or replication push for Postgres. The push against PgBouncer is that you don't need it, unless you do. If you have an app-level connection pool, you probably don't need PgBouncer.