| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
| Cc: | Alexander Stanier <alexander(dot)stanier(at)egsgroup(dot)com>, Dave Cramer <pg(at)fastcrypt(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Change in Log Format and Prepared Statements |
| Date: | 2012-09-19 06:32:06 |
| Message-ID: | 16243.1348036326@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> writes:
> On 09/17/2012 02:45 PM, Alexander Stanier wrote:
>> Does anyone know what the three durations specifically represent?
> I have no idea, honestly. Maybe ask on pgsql-general ?
Parse, bind, execute phases of extended-query protocol?
http://www.postgresql.org/docs/9.2/static/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY
> I strongly agree. Three separate log lines for timing, with no
> indication about which is which, sucks.
AFAICT from looking at the backend code, they are labeled ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | GEISINGER Marc - Contractor | 2012-09-20 11:25:19 | Bug in AbstracJdbc2Statement.replaceProcessing when using dollar quoting? |
| Previous Message | Craig Ringer | 2012-09-19 05:25:55 | Re: Change in Log Format and Prepared Statements |