Skip site navigation (1) Skip section navigation (2)

Re: configure.in / xml / quoting trouble

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: configure.in / xml / quoting trouble
Date: 2007-07-20 17:59:38
Message-ID: 11619.1184954378@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:
> Also, what was the danger with linking pthread?

Basically, the worry with code that wants thread support is that it
might actually try to use that support, and the backend in general will
not survive that (no threading protections).  Also, depending on your
platform, linking in thread support might incur some generalized
overhead costs even when it's not being used; for instance the malloc
functions might start using mutexes.

			regards, tom lane

In response to

pgsql-patches by date

Next:From: Magnus HaganderDate: 2007-07-20 20:35:59
Subject: Re: SSPI authentication - patch
Previous:From: Patrick WelcheDate: 2007-07-20 17:32:39
Subject: Re: configure.in / xml / quoting trouble

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group