Re: Libpq and multithreading

Поиск
Список
Период
Сортировка
От Alban Hertroys
Тема Re: Libpq and multithreading
Дата
Msg-id CAF-3MvOocoxh4moZqKXN3=Y9YHqbi0PqPjmrEHJ7ytzg9yA+JA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Libpq and multithreading  (Asia <asia123321@op.pl>)
Ответы Re: Libpq and multithreading
Список pgsql-general
Дерево обсуждения
An access violation means that you're trying to access memory that doesn't belong to your process. I'm not sure where it's originating, that could be the server but I suspect the issue is at the client-side.

You're probably just forgetting to free memory somewhere.


On 14 January 2013 13:50, Asia <asia123321@op.pl> wrote:
I am using 2 threads, each declares seperate PGconn conenction object.

It connects e.g. 60 times, one connection from one thread, the other connection from the other thread, usually one after each other.
And it fails at 61'st connection with access violation.

I already tried with PQconnect and PQsetdbLogin. I am using mututal SSL authentication with this connections, maybe this is the case?

Kind regards,
Joanna




--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



--
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.

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

Предыдущее
От: Asia
Дата:
Сообщение: Re: Libpq and multithreading
Следующее
От: Merlin Moncure
Дата:
Сообщение: Re: Libpq and multithreading