| From: | Ericson Smith <eric(at)did-it(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Postgresql Logging |
| Date: | 2004-05-26 18:30:26 |
| Message-ID: | 40B4E242.6000700@did-it.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
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(at)did-it(dot)com | RAM should go to everyone! |
| 516-255-0500 | - Sascga Segan |
+-----------------------+----------------------------+
| Attachment | Content-Type | Size |
|---|---|---|
| eric.vcf | text/x-vcard | 315 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-05-26 18:46:01 | Re: Postgresql Logging |
| Previous Message | Frank Finner | 2004-05-26 17:46:32 | Re: performance very slow |