Re: log_duration is redundant, no?
| От | Guillaume Smet |
|---|---|
| Тема | Re: log_duration is redundant, no? |
| Дата | |
| Msg-id | 1d4e0c10609151526m4a92a7f2l518d697d87a93a01@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: log_duration is redundant, no? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: log_duration is redundant, no?
|
| Список | pgsql-hackers |
On 9/8/06, Tom Lane <tgl@sss.pgh.pa.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
В списке pgsql-hackers по дате отправления: