"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> My conclusion is that stats_command_string overhead is non-negligible
>> for simple commands. So I stand by my previous opinion that it should
>> not be turned on without the DBA taking explicit action to turn it on.
> How about with the stats_collector on? ie. Recording block and row level
> stats?
Didn't measure that, but I believe the block/row stats are dumped to the
collector once per transaction, so the overhead ought to be roughly
comparable to this test.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
