| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
|---|---|
| To: | alvin(dot)yk(at)gmail(dot)com | 
| Cc: | pgsql-performance(at)postgresql(dot)org | 
| Subject: | Re: 8.0.1 performance question. | 
| Date: | 2005-04-04 15:49:21 | 
| Message-ID: | 26421.1112629761@sss.pgh.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-jdbc pgsql-performance | 
<alvin(dot)yk(at)gmail(dot)com> writes:
> As a result, I modified log_statement to all.  Without my application
> doing anything, 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(%'
Better ask about that on pgsql-jdbc.  I suppose this is the trace of the
JDBC driver trying to find out column metadata ... but if it's failing
to cache the information that's a pretty serious performance hit.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | alvin.yk | 2005-04-04 16:00:39 | 8.0.1 performance question. | 
| Previous Message | Nico | 2005-04-04 11:56:43 | Re: Another java connect problem | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-04-04 15:52:59 | Re: Sustained inserts per sec ... ? | 
| Previous Message | Hannes Dorbath | 2005-04-04 15:18:24 | Re: Query Optimizer Failure / Possible Bug |