| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | David Parker <dparker(at)tazznetworks(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Increasing the length of |
| Date: | 2004-12-01 16:47:12 |
| Message-ID: | 200412011647.iB1GlCq06535@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Parker wrote:
> How difficult would it be to make the combination
>
> log_statement = all
> log_duration = true
>
> just put the duration on the same line as the statement? Then
> log_min_duration_statement could be used to
> do the desired log-at-threshold behavior, which certainly seems
> valuable. You'd need a way to visually/scriptually (?) distinguish those
> log records, though, I guess.
>
> Note that my original post on this was more of a question than an
> objection - it's entirely possible to sed around having duration and
> statement on separate lines - I just wanted clarification. Having them
> on the same line IS handy, however....
Many people want the statement printed when it starts (for real-time
server monitoring), not when it finishes, meaning we don't know the
duration at start time.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antti Salmela | 2004-12-01 17:24:15 | Index used incorrectly with regular expressions on 7.4.6 |
| Previous Message | Jan Wieck | 2004-12-01 16:43:01 | Re: Error handling in plperl and pltcl |