Re: Bump soft open file limit (RLIMIT_NOFILE) to hard limit on startup

From: "Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl>
To: "Andres Freund" <andres(at)anarazel(dot)de>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tomas Vondra" <tomas(at)vondra(dot)me>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bump soft open file limit (RLIMIT_NOFILE) to hard limit on startup
Date: 2025-02-24 09:56:23
Message-ID: D80L44E10W12.35QIRYPTCJO4P@jeltef.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu Feb 20, 2025 at 1:37 AM CET, Andres Freund wrote:
> I've pushed this, with one trivial modification: I added %m to the error
> message in case setrlimit() fails. That's really unlikely to ever happen, but
> ...

Great! Attached are the updated other patches, I think I addressed all
feedback.

Attachment Content-Type Size
v4-0001-Adds-a-helper-for-places-that-shell-out-to-system.patch text/x-patch 5.8 KB
v4-0002-Bump-postmaster-soft-open-file-limit-RLIMIT_NOFIL.patch text/x-patch 12.9 KB
v4-0003-Reflect-the-value-of-max_safe_fds-in-max_files_pe.patch text/x-patch 1.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2025-02-24 10:07:33 Re: PATCH: warn about, and deprecate, clear text passwords
Previous Message Amit Kapila 2025-02-24 09:49:49 Re: long-standing data loss bug in initial sync of logical replication