From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | alvin(dot)yk(at)gmail(dot)com |
Cc: | pgsql-jdbc(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: 8.0.1 performance question. |
Date: | 2005-04-04 16:15:40 |
Message-ID: | Pine.BSO.4.56.0504041109140.4842@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc pgsql-performance |
On Tue, 5 Apr 2005 alvin(dot)yk(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Thomas | 2005-04-04 16:25:19 | Re: Another java connect problem |
Previous Message | alvin.yk | 2005-04-04 16:00:39 | 8.0.1 performance question. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-04-04 16:23:27 | Re: Sustained inserts per sec ... ? |
Previous Message | Christopher Petrilli | 2005-04-04 16:09:35 | Re: Sustained inserts per sec ... ? |