Re: Aim of --enable-thread-safety ? - Mailing list pgsql-general

From Christopher Browne
Subject Re: Aim of --enable-thread-safety ?
Date
Msg-id 874pxpzkkc.fsf@wolfe.cbbrowne.com
Whole thread Raw
In response to Aim of --enable-thread-safety ?  (DANTE Alexandra <Alexandra.Dante@bull.net>)
Responses Re: Aim of --enable-thread-safety ?  (Bruce Momjian <bruce@momjian.us>)
List 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 by date:

Previous
From: DANTE Alexandra
Date:
Subject: Background Writer and performances
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Background Writer and performances