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 8AEA653455 for ; Mon, 4 Apr 2005 17:44:30 +0100 (BST) 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 86452-08 for ; Mon, 4 Apr 2005 16:44:28 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by svr1.postgresql.org (Postfix) with ESMTP id BB0AE533E0 for ; Mon, 4 Apr 2005 17:44:26 +0100 (BST) Received: by zproxy.gmail.com with SMTP id 9so330029nzo for ; Mon, 04 Apr 2005 09:44:26 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=KR0XseK7xQ9Mr8mveBrAzxod2oIUSdz4uQX/sfxagweJga5l6EPbhK+iz1Yw2cKWFO0NYqX/axsCc0+SjL9o/P4NQOmB0B53VSmv/ykkEdK64agqnhjIP39zbttpgV9aKNiux+xmeFgcdXV/zUckzGfE/yV7bVrPFG6OBg7S67w= Received: by 10.36.37.6 with SMTP id k6mr68661nzk; Mon, 04 Apr 2005 09:44:26 -0700 (PDT) Received: by 10.36.31.14 with HTTP; Mon, 4 Apr 2005 09:44:26 -0700 (PDT) Message-ID: Date: Tue, 5 Apr 2005 00:44:26 +0800 From: Reply-To: To: Kris Jurka Subject: Re: 8.0.1 performance question. Cc: pgsql-jdbc@postgresql.org, pgsql-performance@postgresql.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <26421.1112629761@sss.pgh.pa.us> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.389 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, NO_REAL_NAME, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/16 X-Sequence-Number: 12623 Thank you for the quick response. To help me debug what's happening, can you tell me what's the difference between the 7.4 and 8.0 jdbc drivers in this regard? Is this something that is newly introduced in 8.0? Or is this something that has always been happening? Thanks. On Apr 5, 2005 12:15 AM, Kris Jurka wrote: > > > On Tue, 5 Apr 2005 alvin.yk@gmail.com wrote: > > > I see statements below being executed non-stop. Who is triggering these > > statemetns? Is this normal? What am I doing wrong? > > > > > > 2005-04-04 18:05:00 CST PARSELOG: statement: SELECT attnotnull FROM > > pg_catalog.pg_attribute WHERE attrelid = $1 AND attnum = $2 > > 2005-04-04 18:05:00 CST PARSELOG: statement: SELECT def.adsrc FROM > > pg_catalog.pg_class c JOIN pg_catalog.pg_attribute a ON > > (a.attrelid=c.oid > > ) LEFT JOIN pg_catalog.pg_attrdef def ON (a.attrelid=def.adrelid AND > > a.attnum = def.adnum) WHERE c.oid = $1 and a.attnum = $2 AND def.adsrc > > L > > IKE '%nextval(%' > > These are the results of ResultSetMetaData.isNullable() and > isAutoIncrement(), which your code is apparently calling. The results of > these calls are cached on a per ResultSet data. We have discussed > caching them at a higher level, but couldn't find a way to know when to > flush that cache. > > Kris Jurka >