Re: Extended protocol logging
От | Dave Cramer |
---|---|
Тема | Re: Extended protocol logging |
Дата | |
Msg-id | 27F12005-DB72-4FE2-AED7-37E865AC7C5D@fastcrypt.com обсуждение исходный текст |
Ответ на | Re: Extended protocol logging (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On 31-Oct-06, at 11:51 PM, Tom Lane wrote: > Dave Cramer <pg@fastcrypt.com> writes: >> These are logs from Beta 2. > > With what logging settings? log_duration has rather different > behavior > from what it used to do. to be honest I don't know, and looking at the logs I suspect that this is just logging duration, however it's still looking pretty ambiguous. ( I will get the settings, my client is on the other side of the world) what exactly does it mean ? The total operation was 4.365ms and the parse was .672 and bind was .128? Is it possible for different connections to be interleaved? I still think having the parse, bind,execute show the statement name makes sense if for no other reason than clarity. I would think writing a log parser would be fairly challenging without them. Dave > > regards, tom lane > > ---------------------------(end of > broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster >
В списке pgsql-hackers по дате отправления: