"Guillaume Smet" <[EMAIL PROTECTED]> writes: > Is it normal that when I set log_duration to on and log_statement to > all, I have the following output when I prepare/bind/execute a > prepared statement using the protocol: > LOG: duration: 0.250 ms > LOG: duration: 0.057 ms > LOG: execute my_query: SELECT * FROM shop WHERE $1 = $2 > DETAIL: parameters: $1 = 'Clothes Clothes Clothes', $2 = 'Joe''s Widgets'
> I suppose the first line is the prepare and the second line is the > bind but I'm not sure it's the desired behaviour. Well, considering that the parse and bind may take longer than the execute, I hardly think we want to ignore them for log_duration purposes. And we agreed that if log_duration is on and log_min_duration_statement is not triggered, log_duration should print *only* duration. So I'm not sure what else you expected. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org