[EMAIL PROTECTED] (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 "[EMAIL PROTECTED]" "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! ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
