Currently we are logging SQL statements for profiling purposes. We now get something like this:
2004-05-26 13:27:51 [30017] LOG: statement: SELECT * FROM cache_62 WHERE key='6832271710644150012240e7153b6f62'
2004-05-26 13:27:51 [30017] LOG: duration: 0.733 ms
Is there a way to get the duration into the statement line as well? Sometimes the logging overlaps, so its difficult to decide which duration applies to which statement, even though the have the PID in there.
--
Warmest regards, Ericson Smith
Tracking Specialist/DBA
+-----------------------+----------------------------+
| http://www.did-it.com | RAM is cheap. RAM is fun |
| eric@did-it.com | RAM should go to everyone! |
| 516-255-0500 | - Sascga Segan |
+-----------------------+----------------------------+
begin:vcard fn:Ericson Smith n:Smith;Ericson org:Did-it.com;Programming adr:#304;;55 Maple Avenue;Rockville Center;NY;11570;USA email;internet:eric@did-it.com title:Web Developer tel;work:516-255-0500 tel;cell:646-483-3420 note:Nothing special! x-mozilla-html:FALSE url:http://www.did-it.com version:2.1 end:vcard
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
