Re: log_min_duration_statement oddity
От | Csaba Nagy |
---|---|
Тема | Re: log_min_duration_statement oddity |
Дата | |
Msg-id | 1129795730.27587.146.camel@coppola.muc.ecircle.de обсуждение исходный текст |
Ответ на | Re: log_min_duration_statement oddity (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: log_min_duration_statement oddity
|
Список | pgsql-general |
Thanks Tom, now at least I can stop chasing what I'm doing wrong :-) BTW, will be a way to also log the parameter values for prepared statements ? While debugging performance problems it would be invaluable, in many cases it would help me reproduce the problem when only SOME values cause problems. Thanks, Csaba. On Wed, 2005-10-19 at 20:22, Tom Lane wrote: > Csaba Nagy <nagy@ecircle-ag.com> writes: > > Now the remote connections are coming from Java (the JDBC driver), > > Oh, there's your problem. 8.0 doesn't have very good support for > logging the extended-query protocol, which is what recent versions > of the JDBC driver like to use. 8.1 will be better I believe. > > If you're desperate to get some info, you could force the driver to > fall back to V2 frontend protocol. See the archives for details. > > regards, tom lane
В списке pgsql-general по дате отправления: