Search Postgresql Archives

Re: Aim of --enable-thread-safety ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alexandra.Dante@xxxxxxxx (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!


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux