Re: Libpq and multithreading - Mailing list pgsql-general

From Alban Hertroys
Subject Re: Libpq and multithreading
Date
Msg-id CAF-3MvOocoxh4moZqKXN3=Y9YHqbi0PqPjmrEHJ7ytzg9yA+JA@mail.gmail.com
Whole thread Raw
In response to Re: Libpq and multithreading  (Asia <asia123321@op.pl>)
Responses Re: Libpq and multithreading  (Merlin Moncure <mmoncure@gmail.com>)
List 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 by date:

Previous
From: Asia
Date:
Subject: Re: Libpq and multithreading
Next
From: Merlin Moncure
Date:
Subject: Re: Libpq and multithreading