Re: Deadlock in libpq

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема Re: Deadlock in libpq
Дата
Msg-id AANLkTimnj8XOhC-FtDiXj8=7po03PRH5462kqbzY3JZZ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Deadlock in libpq  (Merlin Moncure <mmoncure@gmail.com>)
Ответы Re: Deadlock in libpq  (Merlin Moncure <mmoncure@gmail.com>)
Список pgsql-general
On Thu, Mar 24, 2011 at 11:52 AM, Merlin Moncure <mmoncure@gmail.com> wrote:
>> As far as connections getting dropped: yes, this sounds reasonable,
>> but given that both the client and the server are running on the same
>> machine, will connections (to 127.0.0.1) really be dropped once every
>> 100.000 or so?
>
> No, don't bother, I forgot the default behavior was to do both, which
> is probably correct in your case. InitSSL just signals if you want
> them to be done.
>
> libpq refcounts connections and does SSL initialization when
> connection count goes from 0->1 and destruction when it goes from
> 1->0.  This operation is protected with mutex (you *are* using thread
> safe libpq, right?).

meh, you have to be -- the locking stuff only gets set up w/thread
safe libpq.  It's basically impossible for that refcount to get thrown
off aiui.  hm.  I'm going back to thinking tom was right and this is
threading issue in the app...maybe there is something you haven't
considered?

merlin

merlin

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

Предыдущее
От: Merlin Moncure
Дата:
Сообщение: Re: Deadlock in libpq
Следующее
От: Emre Hasegeli
Дата:
Сообщение: Re: which view is used another views