Re: stats_command_string default?
| От | Tom Lane |
|---|---|
| Тема | Re: stats_command_string default? |
| Дата | |
| Msg-id | 28529.1045423584@sss.pgh.pa.us обсуждение |
| Ответ на | Re: stats_command_string default? (Kevin Brown <kevin@sysexperts.com>) |
| Ответы |
Re: stats_command_string default?
|
| Список | pgsql-hackers |
Kevin Brown <kevin@sysexperts.com> writes:
> Tom Lane wrote:
>> Kevin Brown <kevin@sysexperts.com> writes:
>>> Would it make more sense to enable stats_command_string by default?
>>
>> I'd vote against it. If we turn it on by default, people are paying
>> for a feature they may not even know exists. Once they find out about
>> it and decide they want it, they can turn it on easily enough.
> The difference in time over 100000 passes was 20 seconds (44 seconds
> with stats_command_string turned on, 24 with it turned off), for an
> impact of 0.2 milliseconds per command executed.
In other words, more than an eighty percent penalty on simple commands.
Not negligible in my book.
> I have no idea if that's small enough to be considered negligible or
> not, considering the hardware it was running on.
I would imagine that the CPU-time ratio would not depend all that much
on the particular hardware.
regards, tom lane
В списке pgsql-hackers по дате отправления: