5 ms·

HN is the worst echo chamber around. Obsessed with this "you must use PostgreSQL for every use case" nonsense. And that anyone who actually has unique data ne

HN is the worst echo chamber around. Obsessed with this "you must use PostgreSQL for every use case" nonsense. And that anyone who actually has unique data needs is simply doing it for their resume or are over-engineering.

paulryanrogers 2y ago
> Obsessed with this "you must use PostgreSQL for every use case" nonsense. Pg fans are certainly here asking "why not PG?". Yet so are fans of other DBs; like DuckDB, CouchDB, SQLite, etc.
- internet101010 2y ago
  I don't see so much DuckDB and CouchDB proselytizing but the SQLite force always out strong. I tend to divide the Postgres vs. SQLite decision on if the data in question is self-contained. Like am I pulling data from elsewhere (Postgres) or am I creating data within the application that is only used for the functionality of said application (SQLite).
  - int_19h 2y ago
    SQLite, in addition to just being plain popular, is a fairly natural stepping stone - you get a lot of fundamental benefits of an SQL RDBMS (abstract high-level queries, ACID etc) without the overhead of maintaining a database server. Postgres is the next obvious stepping stone after that, and the one where the vast majority of actual real-world cases that are not hypotheticals end up fitting.
  - assmanreturns 2y ago
    I think differently. If multiple users need to query the database directly then postgres. If no one is ever going to look at the db except one person or one application then sqllite. It's an interesting question as to whether micro services should be sqllite. Postgres is recommended because it's free, easy to maintain, install and it's has excellent query features.
citizen_friend 2y ago
Nobody is saying this. > who actually has unique data needs We are saying this is probably not true, and you just want to play with toys rather than ship working systems. Google search, cannot be built in Postgres.

paulryanrogers 2y ago

> Obsessed with this "you must use PostgreSQL for every use case" nonsense. Pg fans are certainly here asking "why not PG?". Yet so are fans of other DBs; like DuckDB, CouchDB, SQLite, etc.

internet101010 2y ago
I don't see so much DuckDB and CouchDB proselytizing but the SQLite force always out strong. I tend to divide the Postgres vs. SQLite decision on if the data in question is self-contained. Like am I pulling data from elsewhere (Postgres) or am I creating data within the application that is only used for the functionality of said application (SQLite).
- int_19h 2y ago
  SQLite, in addition to just being plain popular, is a fairly natural stepping stone - you get a lot of fundamental benefits of an SQL RDBMS (abstract high-level queries, ACID etc) without the overhead of maintaining a database server. Postgres is the next obvious stepping stone after that, and the one where the vast majority of actual real-world cases that are not hypotheticals end up fitting.
- assmanreturns 2y ago
  I think differently. If multiple users need to query the database directly then postgres. If no one is ever going to look at the db except one person or one application then sqllite. It's an interesting question as to whether micro services should be sqllite. Postgres is recommended because it's free, easy to maintain, install and it's has excellent query features.

citizen_friend 2y ago

Nobody is saying this. > who actually has unique data needs We are saying this is probably not true, and you just want to play with toys rather than ship working systems. Google search, cannot be built in Postgres.