pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: chenyanfei <postgresql_2016@163.com>
To: pgsql-bugs@postgresql.org
Subject: syslogger file descriptor question
Date: Thu, 29 Apr 2021 19:16:31 -0700 (MST)
Message-ID: <1619748991620-0.post@n3.nabble.com> (raw)

When use the  pg_ctl start -l  command to start the postgres, I find the
syslogger process point to the specified log file.


With long time running, the log file is too big. So we delete it, but the fd
is show as deleted.


It looks like the file descriptor leak. Although this problem has little
impact, it brings troubles to customers. 
The regular file has the rotate mechanism, so it can close the old fd and
reopen the new file.

My question is if I specify them to /dev/null whether have any problem. I
find one process do this not in first start.




--
Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html





view thread (3+ messages)  latest in thread

Message-ID: <1619748991620-0.post@n3.nabble.com>
Permalink:  ../1619748991620-0.post@n3.nabble.com/
Also on:    postgresql.org/message-id/1619748991620-0.post@n3.nabble.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: postgresql_2016@163.com
  Subject: Re: syslogger file descriptor question
  In-Reply-To: <1619748991620-0.post@n3.nabble.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox