Re: Aim of --enable-thread-safety ?
От | Christopher Browne |
---|---|
Тема | Re: Aim of --enable-thread-safety ? |
Дата | |
Msg-id | 874pxpzkkc.fsf@wolfe.cbbrowne.com обсуждение исходный текст |
Ответ на | Aim of --enable-thread-safety ? (DANTE Alexandra <Alexandra.Dante@bull.net>) |
Ответы |
Re: Aim of --enable-thread-safety ?
|
Список | pgsql-general |
Alexandra.Dante@bull.net (DANTE Alexandra) wrote: > I wonder if this compilation option is really taken into account as > PostgreSQL is not multi-threading but multi-processing. > I have read that without this option, the libpq won't know anything > about threads and may indeed have problems, but could you explain me > how this option runs ? > It is not clear for me the aim of this option in an multi-processing > environment... > Is it possible to force PostgreSQL to be multi-threaded ? This option is all about allowing you to have multi-threaded *client* applications. That is, applications that many have multiple threads where threads can hold onto database connections. -- (format nil "~S@~S" "cbbrowne" "linuxfinances.info") http://cbbrowne.com/info/internet.html Q: How many Newtons does it take to change a light bulb? A: Faux! There to eat lemons, axe gravy soup!
В списке pgsql-general по дате отправления: