Re: Printing query durations
От | Dave Cramer |
---|---|
Тема | Re: Printing query durations |
Дата | |
Msg-id | FC0183F9-41C7-4EC3-B6E7-6EC2A5142D2E@fastcrypt.com обсуждение исходный текст |
Ответ на | Re: Printing query durations (Simon Riggs <simon@2ndquadrant.com>) |
Ответы |
Re: Printing query durations
|
Список | pgsql-jdbc |
Simon, What happens if I turn log_duration on ? Doesn't it prepend the duration to every log ? Dave On 28-Mar-06, at 5:32 AM, Simon Riggs wrote: > On Tue, 2006-03-28 at 13:26 +1200, Kevin Dorne wrote: > >> I am having some trouble getting PostgreSQL to log durations with >> statements when called through JDBC. They appear just fine with >> interactive queries using psql, but the duration field does not >> show up >> on JDBC queries. >> >> Is there some configuration I need to pass to the JDBC driver? > > These two logging formats are each produced by different parameters: > >> Example output from an interactive query: >> LOG: duration: 109.524 ms statement: SELECT count(*) FROM >> transaction; > > This is produced by log_min_duration_statement > -1 > These lines always have duration prefixes. > >> Example output from a JDBC query: >> LOG: statement: SELECT count(*) FROM transaction; > > This is produced by log_statement = 'all' > These lines never have durations. > If you want the matching durations, use log_duration = on and read the > manual to see how to match them up. > > The same statement can be logged twice using those options. > > http://www.postgresql.org/docs/8.1/static/runtime-config- > logging.html#RUNTIME-CONFIG-LOGGING-WHAT > > Does that answer your query? > > Best Regards, Simon Riggs > > > ---------------------------(end of > broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that > your > message can get through to the mailing list cleanly >
В списке pgsql-jdbc по дате отправления: