From: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: log_duration is redundant, no? |
Date: | 2006-09-15 22:26:00 |
Message-ID: | 1d4e0c10609151526m4a92a7f2l518d697d87a93a01@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/8/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It's done already ...
(Working on implementing the last changes you made in formatting in pgFouine)
Is it normal that when I set log_duration to on and log_statement to
all, I have the following output when I prepare/bind/execute a
prepared statement using the protocol:
LOG: duration: 0.250 ms
LOG: duration: 0.057 ms
LOG: execute my_query: SELECT * FROM shop WHERE $1 = $2
DETAIL: parameters: $1 = 'Clothes Clothes Clothes', $2 = 'Joe''s Widgets'
I suppose the first line is the prepare and the second line is the
bind but I'm not sure it's the desired behaviour.
Any comment?
--
Guillaume
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-15 22:30:09 | Re: log_duration is redundant, no? |
Previous Message | Tom Lane | 2006-09-15 22:22:31 | Re: [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase 's' |