From: | Christian Dannemann <Christian(at)merus(dot)co(dot)uk> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | prepared statements |
Date: | 2006-12-12 15:08:37 |
Message-ID: | 457EC5F5.9090402@merus.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hello All,
We are currently experimenting with a postgresql cluster database
(pgcluster 1.5rc11).
The cluster replicates all prepared statements across all database
servers (which makes sense if they are for updates and inserts). It also
does this for normal select statements.
That means that when using prepared statements, there is absolutely NO
gain from using a db cluster. Everything is executed in every database.
And there is the additional overhead of replicating that across. So huge
investment in hardware, and a performance loss is the gain from that :-(
Our application is written in java and we use the jdbc postgresql driver.
Now it appears that this driver issues ANY statement as a prepared
statement. I've tried to switch this off but to no avail. This is a huge
nightmare and I don't quite understand why it is deemed necessary to
issue every simple select statement as a prepared statement.
Maybe someone on this mailing list can enlighten me?
Kind Regards,
Christian
--
Christian Dannemann
Managing Director
Merus Software Ltd
Phone: +44 (0)1453 708 600
DDI: +44 (0)1453 708 610
VoIP: christian(at)sip(dot)merus(dot)co(dot)uk
http://www.merus.co.uk
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2006-12-12 16:26:06 | Re: prepared statements |
Previous Message | Paul Thomas | 2006-12-12 11:14:29 | Re: web-app not working after upgrade 7.4 to 8.1 |