Re: [GENERAL] log_min_duration_statement oddity

2005-10-24 Thread Bruce Momjian
Csaba Nagy wrote: > 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 You mean the BIND values? No, not in 8.1, but it is on our TODO list now.

Re: [GENERAL] log_min_duration_statement oddity

2005-10-20 Thread Csaba Nagy
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.

Re: [GENERAL] log_min_duration_statement oddity

2005-10-19 Thread Tom Lane
Csaba Nagy <[EMAIL PROTECTED]> 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 bel

Re: [GENERAL] log_min_duration_statement oddity

2005-10-19 Thread Csaba Nagy
Well, I'm completely sure that long running queries from local connections are logged, as I can see them in the log file. Quick queries are not logged even for local connections, I tested that too... And I'm also sure that I do have long running queries on remote connections, our application logged

Re: [GENERAL] log_min_duration_statement oddity

2005-10-19 Thread Tom Lane
Csaba Nagy <[EMAIL PROTECTED]> writes: > I wonder if I understood correctly what log_min_duration_statement > does... I set it to 2000, and the result is that all queries running > more than 2 seconds on _local_ connections are logged, but long running > queries on remote connections are not logged