| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: log_duration |
| Date: | 2005-02-08 00:40:39 |
| Message-ID: | KGEFLMPJFBNNLNOOOPLGCEIMCIAA.simon@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>Tom Lane
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> > Further update on this:
>
> > We've isolated this issue to JDBC client access.
>
> Ah-hah, now it makes sense. I believe the JDBC driver always uses
> extended query protocol (parse/bind/execute messages).
Thanks for the *solution.
I had a D'Oh moment about 2 hours after I posted...
> As a quick workaround until someone thinks of a better idea,
> it might be
> sufficient to attach logging code to the execute phase, and ignore the
> partial-execution issue.
Done... we're getting results out now.
I'm logging both duration of execution and the statement text, as would
be displayed in pg_stat_activity.
Thanks,
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robby Russell | 2005-02-08 03:42:32 | Re: [GENERAL] PHP/PDO Database Abstraction Layer |
| Previous Message | Joshua D. Drake | 2005-02-07 22:02:54 | PHP/PDO Database Abstraction Layer |