Re: Reasoning behind process instead of thread based - Mailing list pgsql-general

From nd02tsk@student.hig.se
Subject Re: Reasoning behind process instead of thread based
Date
Msg-id 4194.130.243.12.138.1098899223.squirrel@130.243.12.138
Whole thread Raw
In response to Re: Reasoning behind process instead of thread based  ("Scott Marlowe" <smarlowe@qwest.net>)
Responses Re: Reasoning behind process instead of thread based  (Martijn van Oosterhout <kleptog@svana.org>)
Re: Reasoning behind process instead of thread based  (Thomas Hallgren <thhal@mailblocks.com>)
List pgsql-general
>Two:  If a
> single process in a multi-process application crashes, that process
> alone dies.  The buffer is flushed, and all the other child processes
> continue happily along.  In a multi-threaded environment, when one
> thread dies, they all die.


So this means that if a single connection thread dies in MySQL, all
connections die?

Seems rather serious. I am doubtful that is how they have implemented it.




pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Reasoning behind process instead of thread based
Next
From: Alvaro Herrera
Date:
Subject: Re: page locking? too many btree indexes...