Brian-
I'm not sure if this will help the performance, but I believe this statement
is equivalent:
update v set nl=nl+1 where exists (select 'x' from l where l.sid = v.id and
l.did = 123456);
-Nick
--
Nick Fankhauser [EMA
Okay, maybe it is just me, but I think that something is wrong with the
way a plan is generated for the following update:
EXPLAIN UPDATE v SET nl=nl+1 WHERE id IN (SELECT sid FROM l WHERE did =
123456) ;
NOTICE: QUERY PLAN:
Seq Scan on v (cost=0.00..1884077041.93 rows=2873155 width=38)
Sub
James-
We're using the Tomcat servlet engine & have had no similar problems, So I
think you can eliminate the JDBC driver from your list & focus on Resin or
something in your code.
We also quickly decided that we needed to be using a connection pool for a
web app. Opening & closing connections r
We seem to be having an issue with the JDBC driver, Resin 2.0.5 servlet
engine, and/or postgres 7.1.2.
Basically what happens is this. In the Java Servlet code, the programmers
are making an explicit close connection call to the database through the
JDBC driver (As they should). Now! When the cod
On 18 Apr 2002 at 15:40, Rommel B. Abaya wrote:
> Hi,
>
> I'm trying to find out if database mirroring could be done with
> PostgreSQL. What i mean is that when my applications
> insert/delete/update records in my production server, it will also
> insert/delete/update the same in my development
