pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
interpret statement log duration information
2+ messages / 2 participants
[nested] [flat]

* interpret statement log duration information
@ 2010-10-25 22:33 Mark Rostron <mrostron@ql2.com>
  2010-10-25 22:54 ` Re: interpret statement log duration information Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 2+ messages in thread

From: Mark Rostron @ 2010-10-25 22:33 UTC (permalink / raw)
  To: pgsql-performance

Hey

Turned on log_min_duration_statement today and started getting timings on sql statements (version 8.3.10).
Can anyone please tell me how to interpret the (S_nn/C_nn) information in the log line.

LOG:  duration: 19817.211 ms  execute S_73/C_74: ....(statement text) .....

Thanks for your time
Mr

^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: interpret statement log duration information
  2010-10-25 22:33 interpret statement log duration information Mark Rostron <mrostron@ql2.com>
@ 2010-10-25 22:54 ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 2+ messages in thread

From: Tom Lane @ 2010-10-25 22:54 UTC (permalink / raw)
  To: Mark Rostron <mrostron@ql2.com>; +Cc: pgsql-performance

Mark Rostron <mrostron@ql2.com> writes:
> Can anyone please tell me how to interpret the (S_nn/C_nn) information in the log line.

> LOG:  duration: 19817.211 ms  execute S_73/C_74: ....(statement text) .....

It's prepared statement name slash portal name.  You'd have to look at
your client-side code to find out what the names refer to.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2010-10-25 22:54 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-10-25 22:33 interpret statement log duration information Mark Rostron <mrostron@ql2.com>
2010-10-25 22:54 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox