From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Emanuel Calvo <postgres(dot)arg(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Additional information on log_line_prefix |
Date: | 2013-11-14 19:07:14 |
Message-ID: | 20131114190714.GH24549@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Oct 25, 2013 at 02:58:12PM -0400, Andrew Dunstan wrote:
>
> On 10/25/2013 01:50 PM, Emanuel Calvo wrote:
> >
> >Hi guys,
> >
> >I'm working on a quick convertion script for query reviews and I
> >wonder if a feature request to add the following values will be
> >possible:
> >
> > %D = duration
> > %L = lock_time (lock only for this query)
> > %E = estimated rows
> > %R = total rows returned
> > %B = total bytes sent
> > %T = temporal tables used
> >
> >Those prefixes/values are just examples/proposals.
> >
> >Thanks for the hard work!
> >
> >
>
> Pretty much all of this can be got with the auto_explain module, and
> I think that's where it belongs.
The other problem is that these mostly have meaning for a line generated
by a completed query, but not for the many other lines that can appear
in that log file.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2013-11-14 19:17:22 | Re: additional json functionality |
Previous Message | Atri Sharma | 2013-11-14 18:35:08 | Re: WITHIN GROUP patch |