Date: Thu, 29 Apr 2021 19:16:31 -0700 (MST)
From: chenyanfei <postgresql_2016@163.com>
To: pgsql-bugs@postgresql.org
Message-ID: <1619748991620-0.post@n3.nabble.com>
Subject: syslogger file descriptor question
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/1619748991620-0.post%40n3.nabble.com>
Precedence: bulk

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 f=
d
is show as deleted.


It looks like the file descriptor leak. Although this problem has little
impact, it brings troubles to customers.=20
The regular file has the rotate mechanism=EF=BC=8C 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