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.
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.
> 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.
Pg fans are certainly here asking "why not PG?". Yet so are fans of other DBs; like DuckDB, CouchDB, SQLite, etc.
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.
Postgres is recommended because it's free, easy to maintain, install and it's has excellent query features.