we are using jdbc -- the "log_min_duration_statement = 3000 " statement works fine for me. Looks like there's no other work around for the bug(?). Not sure since I have no interest in logging a million statements a day, I only want to see the poorly performing hits.

Doesn't it depend on what jdbc driver you are using?

It depends if he's using new-protocol prepared queries which don't get logged properly. Wasn't that fixed for 8.1 or something?


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?


Reply via email to