Re: libpq thread safety

Поиск
Список
Период
Сортировка
От Manfred Spraul
Тема Re: libpq thread safety
Дата
Msg-id 40296329.4030703@colorfullife.com
обсуждение исходный текст
Ответ на Re: libpq thread safety  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: libpq thread safety  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-hackers
Bruce Momjian wrote:

>However, we really have two types of function tested. 
>The first, strerror, can be thread safe by using thread-local storage
>_or_ by returning pointers to static strings.  The other two function
>tests require thread-local storage to be thread-safe.
>  
>
You are completely ignoring that libpq is a library: what if the app 
itself wants to call gethostbyname or stderror, too?
Right now libpq has it's own private mutex. This doesn't work - the 
locking must be process-wide. The current implementation could be the 
default, and apps that want to use gethostbyname [or kerberos 
authentication, etc.] outside libpq must fill in appropriate callbacks.

--   Manfred



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: libpq thread safety
Следующее
От: "Simon Riggs"
Дата:
Сообщение: Summary of Changes since last release (7.4.1)