On Thu, Feb 12, 2009 at 1:21 AM, Serge Fonville
<serge.fonville@gmail.com> wrote:
> I could not find the reason as to why this way has been chosen by the
> developers
Because separate processes are much more robust than multiple threads.
And on Linux, the difference in performance is minimal. Note some
OSes like Windows, and to a lesser extent, Solaris, have significant
overhead for forking processes, and run multi-threaded apps much
faster.
Since any real db in a heavy lifting situation is probably using a
connection pooler, then the cost of startup of a new process isn't a
big deal, because they're not getting started all the time anymore.
