From: | Christopher Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Aim of --enable-thread-safety ? |
Date: | 2006-07-10 12:54:59 |
Message-ID: | 874pxpzkkc.fsf@wolfe.cbbrowne.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alexandra(dot)Dante(at)bull(dot)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(at)~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!
From | Date | Subject | |
---|---|---|---|
Next Message | DANTE Alexandra | 2006-07-10 12:56:48 | Background Writer and performances |
Previous Message | DANTE Alexandra | 2006-07-10 12:44:05 | Re: Aim of --enable-thread-safety ? |