On Thu, Oct 3, 2019 at 8:30 AM Святослав Ермилин
wrote:
> There is another way to solve this problem:
> We can give users the opportunity to leave or close descriptors.
> I.e. config switch for this. But I think that it's too complicated.
The typical solution to this problem is to send the stdout
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
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
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
=?utf-8?B?0KHQstGP0YLQvtGB0LvQsNCyINCV0YDQvNC40LvQuNC9?=
writes:
> 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 investi
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
