Re: log_line_info plan

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: log_line_info plan
Date: 2004-02-18 03:54:08
Message-ID: 200402180354.i1I3s8P02381@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joshua D. Drake wrote:
> Andrew Dunstan wrote:
> >
> > I am about to redo the patch that would allow tagging of log lines with
> > info via a printf-style string.
> >
> > Current plans are to call the config parameter "log_line_info" and
> > implement the following escapes:
> >
> > %U = user
> > %D = database
> > %T = timestamp
> > %P = pid
> > %L = session log line number
> > %C = sessionid cookie (hex encoded session start time + pid)
> > %S = session start timestamp
> > %I = Command Tag (e.g. "CREATE TABLE")
> >
> > Any comments or suggestions before I start?
>
> My be kind of cool if we a a duration variable in there, especially if
> combined with %I

Duration of what? We could show the duration within the session, but we
don't know the query duration because we print this before the query is
executed, so folks can look in the logs to see what is currently
running.

--
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2004-02-18 04:11:04 Re: log_line_info plan
Previous Message Tom Lane 2004-02-18 03:53:17 Re: CHAR(n) always trims trailing spaces in 7.4