On Thu, Jul 26, 2012 at 1:34 AM, Maciek Sakrejda wrote:
>> unfortunately postgres jdbc is bugged and does not honor the above for
>> transaction control commands (begin, commit, etc). This patch
>> http://treehou.se/~omar/postgresql-jdbc-8.4-701-pgbouncer_txn.patch
>> will fix it, assuming it has
On Wed, Jul 25, 2012 at 7:13 PM, Rural Hunter wrote:
> Why not just use simple Statement instead of PreparedStatement and construct
> the SQL with concated string or StringBuilder? like this:
> int col1=xxx;
> String col2="";
> String sql="select * from table where col1="+col+" and col2='"+col
> unfortunately postgres jdbc is bugged and does not honor the above for
> transaction control commands (begin, commit, etc). This patch
> http://treehou.se/~omar/postgresql-jdbc-8.4-701-pgbouncer_txn.patch
> will fix it, assuming it hasn't been fixed in recent postgres jdbc.
Looks like it's stil
Why not just use simple Statement instead of PreparedStatement and
construct the SQL with concated string or StringBuilder? like this:
int col1=xxx;
String col2="";
String sql="select * from table where col1="+col+" and col2='"+col2+"'";
δΊ 2012/7/26 3:59, Vinicius Abrahao ει:
On Wed, Jul 25
On Wed, Jul 25, 2012 at 2:59 PM, Vinicius Abrahao wrote:
> On Wed, Jul 25, 2012 at 4:26 PM, Merlin Moncure wrote:
>> On Wed, Jul 25, 2012 at 2:17 PM, Vinicius Abrahao
>> wrote:
>>> On Wed, Jul 25, 2012 at 3:45 PM, Merlin Moncure wrote:
> Note that it seems the preparing/planning interactio
On Wed, Jul 25, 2012 at 4:26 PM, Merlin Moncure wrote:
> On Wed, Jul 25, 2012 at 2:17 PM, Vinicius Abrahao
> wrote:
>> On Wed, Jul 25, 2012 at 3:45 PM, Merlin Moncure wrote:
Note that it seems the preparing/planning interaction was not the
poster's actual problem, but it may have been
On Wed, Jul 25, 2012 at 2:17 PM, Vinicius Abrahao wrote:
> On Wed, Jul 25, 2012 at 3:45 PM, Merlin Moncure wrote:
>>> Note that it seems the preparing/planning interaction was not the
>>> poster's actual problem, but it may have been yours. As Tom Lane notes
>>> in that thread, this should get be
On Wed, Jul 25, 2012 at 3:45 PM, Merlin Moncure wrote:
> On Tue, Jul 24, 2012 at 10:50 AM, Maciek Sakrejda
> wrote:
>> This may be another issue of the problem discussed here:
>> http://postgresql.1045698.n5.nabble.com/avoid-prepared-statements-on-complex-queries-td4996363.html
>> (Kris Jurka ex
On Tue, Jul 24, 2012 at 10:50 AM, Maciek Sakrejda wrote:
> This may be another issue of the problem discussed here:
> http://postgresql.1045698.n5.nabble.com/avoid-prepared-statements-on-complex-queries-td4996363.html
> (Kris Jurka explains the crux of it in that thread).
>
> Note that it seems th
This may be another issue of the problem discussed here:
http://postgresql.1045698.n5.nabble.com/avoid-prepared-statements-on-complex-queries-td4996363.html
(Kris Jurka explains the crux of it in that thread).
Note that it seems the preparing/planning interaction was not the
poster's actual proble
ssage and the Closed message.
Brett
From: pgsql-performance-ow...@postgresql.org
[mailto:pgsql-performance-ow...@postgresql.org] On Behalf Of Riaan van den Dool
Sent: Tuesday, 24 July 2012 5:21 PM
To: pgsql-performance@postgresql.org
Subject: [PERFORM] Geoserver-PostGIS performance problems
the Select message and the Closed message.
Brett
From: pgsql-performance-ow...@postgresql.org
[mailto:pgsql-performance-ow...@postgresql.org] On Behalf Of Riaan van den Dool
Sent: Tuesday, 24 July 2012 5:21 PM
To: pgsql-performance@postgresql.org
Subject: [PERFORM] Geoserver-PostGIS performance
Hi
We have noticed something strange in the interaction between our Geoserver
instance and Postgres/PostGIS.
After setting Geoserver's log level to include developer debugging, I managed
to capture a single request from Geoserver WMS to PostGIS.
The (shortened) sequence of events and t
13 matches
Mail list logo
