| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, Postgres JDBC <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Prepared statements, parameters and logging |
| Date: | 2007-06-25 22:07:44 |
| Message-ID: | 46803CB0.2000009@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Csaba Nagy wrote:
(before:)
> duration: 5437.499 ms statement: EXECUTE <unnamed> [PREPARE: SELECT
> ... ]
(after:)
> duration: 2200.570 ms statement: EXECUTE C_220047 [PREPARE: SELECT
> ... ]
Also.. as to why you see the behaviour change, I'd guess that you're
using log_min_duration and the plans for the queries where you are using
setFetchSize() have changed from one with low startup cost to one with
high startup cost due to switching from named to unnamed statements. The
high startup cost plan means the very first portal execution takes
longer and gets logged.. the low startup cost plan might be more
expensive overall but the cost is spread out across all the portal
executions, so no one execution takes long enough to get logged.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Csaba Nagy | 2007-06-26 08:22:25 | Re: Prepared statements, parameters and logging |
| Previous Message | Oliver Jowett | 2007-06-25 21:40:52 | Re: Prepared statements, parameters and logging |