> So, Postgres is using process-per-connection model. Can some explain why this is? And why not something like thread-per-connection? This is explained in thei

> So, Postgres is using process-per-connection model. Can some explain why this is? And why not something like thread-per-connection? This is explained in their Wiki "Things we do NOT want" https://wiki.postgresql.org/wiki/Todo#Features_We_Do_Not_Want https://wiki.postgresql.org/wiki/Todo#Features_We_Do_Not_Wan... > All backends running as threads in a single process (not wanted) > This eliminates the process protection we get from the current setup. Thread creation is usually the same overhead as process creation on modern systems, so it seems unwise to use a pure threaded model, and MySQL and DB2 have demonstrated that threads introduce as many issues as they solve. Threading specific operations such as I/O, seq scans, and connection management has been discussed and will probably be implemented to enable specific performance features.