PostgreSQL is the best DB prove me wrong

>>58917542

>one process per DB connection
>parallel agg not even available until 9.6

Yup. Best DB ever

>>58917871
>one process per DB connection
[citation needed]

>>58917871

Samefagging to add more

>replication is a nightmare and prone to failure in production
>tooling is meh. Pgadmin renders the UI in the main thread causing lockups left and right.
>write amplification problems. See uber switching to mysql saga
>table partitioning is really bad. Querying a base table results in seconds being added to a query over manually specifying the partition

I can keep going

>>58917902
https://www.postgresql.org/docs/8.2/static/connect-estab.html


>PostgreSQLis implemented using a simple"process per user"client/server model. In this model there is oneclient processconnected to exactly oneserver process


Pgbouncer kinda solves but not really. Good luck scaling postgres

>>58917542
How is Euclidean Space that far down

>>58917960
That's one process per user, not one process per DB connection like you said. A user process can have multiple DB connections.

>>58917939
Continued samefagging. Just for clarity I work with postgres daily and came from Microsoft SQL Server which is horrible...

>network timeouts can cause the backend to think the client dropped but the client has no idea the backend has canceled the query

This is a huge problem with python psycopg2 driver, but I've seen it happen in production on JDBC clients as well. Also, I'm not the only one...

https://aphyr.com/posts/282-jepsen-postgres

>"Even though the Postgres server is always consistent, the distributed system composed of the serverandclient together maynotbe consistent. It’s possible for the client and server to disagree about whether or not a transaction took place."


Also

>no columnar storage options out of the box in 2014 + 3

call me 12 but this is fucking hilarious

https://en.wikipedia.org/wiki/Hairy_ball_theorem

fucking mathematicians

>>58918003
Yes. This is a huge problem when you have hundreds of concurrent connections. The overhead for a new OS process is really high

Shameless bump to see if OP still thinks the world of postgres

>>58918287
What else is there to use? MongoDB is shit, m$ sql server is shit.

OP here, every db is shit and I hate all those idiots out there who do benchmarks on default configs.