From: | Nicola Pero <nicola(at)brainstorm(dot)co(dot)uk> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Using JDBC and libpq in the same process |
Date: | 2003-10-09 11:30:24 |
Message-ID: | Pine.LNX.4.44.0310091220310.5308-100000@nicola.brainstorm.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Hi,
I have to work on some software which is using JDBC and libpq (via JNI) in
the same process to connect to the same Postgres database. The software
is heavily multithreaded.
When running under heavy loads and accessing the database under JDBC and
libpq at the same time, we get obscure JVM crashes.
Before I even start debugging this, I wanted to ask - is there any known
fundamental reason why JDBC and libpq should *not* be used at the same
time in the same process ?
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Joseph Krogh | 2003-10-09 12:00:01 | pg_dump error (loading 7.2.2-dump in 7.4b4) |
Previous Message | Peter Eisentraut | 2003-10-09 11:06:46 | Re: _GNU_SOURCE |
From | Date | Subject | |
---|---|---|---|
Next Message | shyamperi | 2003-10-09 12:16:16 | Serious Problem with the windows and postgres configuration |
Previous Message | Roger Bjärevall | 2003-10-09 08:40:17 | DatabaseMetaData.getTypeInfo() question |