News for hackers. Stuff that matters.
Re:Improving Postgres Connection Scalability: Snapshots by hans_castorp on Tuesday October 27, 2020 @03:03AM (#24905036)
FWIW: Oracle also uses one process per connection on Unix/Linux. I think since Oracle 12 this can be changed during installation, but it's still the default.

When using connection pools, this isn't really such a problem in the majority of the cases.

Re:Improving Postgres Connection Scalability: Snapshots by aeyes on Tuesday October 27, 2020 @08:28AM (#24906740)
Oracle doesn't handle TCP connections, the Oracle Net Listener (a separate process) is responsible for that. It supports connection pooling.

I'm no expert on how this scales compared to Postgres as it is hard to find benchmarks, thanks to Oracle licensing terms.

Re:Improving Postgres Connection Scalability: Snapshots by voganmother42 on Tuesday October 27, 2020 @03:07AM (#24905054)
In oracle its been an option for a long time(since atleast 10g, I think before), shared vs dedicated servers in their language, and in my experience pretty rare to use shared servers.
Re:Improving Postgres Connection Scalability: Snapshots by hans_castorp on Tuesday October 27, 2020 @03:49AM (#24905229)
Shared servers represent a built-in connection pool. They still use one process for each connection.

Oracle uses a thread model in Windows (one "orcle" process, each connection is a thread), but not on Unix/Linux.