Extension to monitor errors in log

Hi! I wrote extension for postgresql that is collecting statistics about errors in logfile. This extension counts the number of messages of each type and code. It's designed to enable monitoring tools. I'm going to use it as a data source for plot of number of errors, warnings and fatals. Source

Re: Close stdout and stderr in syslogger

Hi, > In any case, the proposed patch almost certainly introduces new > problems, in that you dropped the fcloses's into code that > executes repeatedly. I guess it's better to place fclose() right after successful syslogger start. In that case we close descriptors just one time. But it's enough

Re: Close stdout and stderr in syslogger

Hi Tom, Thank you for quick reply. > I'm quite certain that the current behavior is intentional, if only > because closing the syslogger's stderr would make it impossible to > debug problems inside the syslogger. Developer who debugs syslogger, probably, can remove fclose() calls. Maybe we can ha

Re: Close stdout and stderr in syslogger

Hi Tom, Thank you for quick reply. > I'm quite certain that the current behavior is intentional, if only> because closing the syslogger's stderr would make it impossible to> debug problems inside the syslogger.Developer who debugs syslogger, probably, can remove fclose() calls.Maybe we can have a s

Close stdout and stderr in syslogger

Hi! Few months ago we have encountered situation when some quite big open log files were open by Postres despite being deleted.This affects free space caluculation in out managed PostgreSQL instances.Currently I'm investigating this issue.We traced some roots to unclosed descriptors in Perl code of