X-Original-To: pgsql-jdbc-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 43575529DA;
	Wed, 17 Aug 2005 02:01:53 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 32118-03; Wed, 17 Aug 2005 05:01:48 +0000 (GMT)
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by svr1.postgresql.org (Postfix) with ESMTP id 1C195529C6;
	Wed, 17 Aug 2005 02:01:45 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j7H51j41012038;
	Wed, 17 Aug 2005 01:01:45 -0400 (EDT)
To: "Barry Lind" <blind@xythos.com>
Cc: pgsql-performance@postgresql.org, pgsql-jdbc@postgresql.org
Subject: Re: Performance problem using V3 protocol in jdbc driver 
In-reply-to: 
 <03E7D3E231BB7B4A915A6581D4296CC6015D534E@NSNOVPS00411.nacio.xythos.com>
References: 
 <03E7D3E231BB7B4A915A6581D4296CC6015D534E@NSNOVPS00411.nacio.xythos.com>
Comments: In-reply-to "Barry Lind" <blind@xythos.com>
	message dated "Tue, 16 Aug 2005 21:42:29 -0700"
Date: Wed, 17 Aug 2005 01:01:45 -0400
Message-ID: <12037.1124254905@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006]
X-Spam-Level: 
X-Archive-Number: 200508/109
X-Sequence-Number: 13678

"Barry Lind" <blind@xythos.com> writes:
> ...  On a hunch I switched the jdbc driver to using the V2 protocol
> and the load on the machine dropped down to what it was when using
> Oracle and everything was fine.

First knee-jerk reaction is that it's an optimization problem stemming
from V3 protocol feeding parameterized queries to the backend where V2
did not, and the planner being unable to cope :-(

Can you identify the specific queries causing the problem?

			regards, tom lane