Campbell, Lance wrote:
> I have noticed a slight spike in the amount of CPU usage in the last few
> weeks. I am sure it has to do with a change or two that was made to
> some queries. What is the best way to log the SQL that is being
> executed?
Take a look at statement_timeout and log_statement configuration variables.
> I would prefer to limit the size of the log file to 2 G. Is
> there a way to do this?
log_rotation_size, together with an external tool to delete old log
files. Or use log_truncate_on_rotation and log_rotation_age instead of
log_rotation_size.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
