Re: log_duration is redundant, no? - Mailing list pgsql-hackers

From Guillaume Smet
Subject Re: log_duration is redundant, no?
Date
Msg-id 1d4e0c10609160456q7ae43357tb19b358b71b2fba5@mail.gmail.com
Whole thread Raw
In response to Re: log_duration is redundant, no?  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On 9/16/06, Alvaro Herrera <alvherre@commandprompt.com> wrote:
> It might make sense to log _what_ is going on, without telling all the
> little details, for example
>
> LOG:  parse duration: 0.250 ms
> LOG:  bind duration: 0.057 ms
> LOG:  execute my_query: SELECT * FROM shop WHERE $1 = $2
> DETAIL:  parameters: $1 = 'Clothes Clothes Clothes', $2 = 'Joe''s Widgets'

It's not really the idea when you use log_statement and log_duration.
Lines are completely different semantically speaking.
So you should have:
LOG:  parse (log_statement)
LOG:  duration: 0.250 ms (log_duration)

--
Guillaume


pgsql-hackers by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: [PATCHES] Tiny plpython fix
Next
From: "Magnus Hagander"
Date:
Subject: Re: [PATCHES] Include file in regress.c