Benefit to increasing max_files_per_process?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



PG 14.13 on RHEL 8.10

max_files_per_process is the default 1000.

Currently, many connection processes are hovering around 990 open files.

Does PG purposefully close some unused files when getting near the max?  Would we see benefits to increasing max_files_per_process as well as running "ulimit -n 2500" (and then of course restarting PG).

I don't see any "too many open files" errors in the log file, but am trying to plan ahead.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

[Index of Archives]     [Postgresql Home]     [Postgresql General]     [Postgresql Performance]     [Postgresql PHP]     [Postgresql Jobs]     [PHP Users]     [PHP Databases]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Yosemite Forum]

  Powered by Linux