Request a Demo
Home   >   mailing lists

Re: Request for Guidance on Recommended ulimit/Open File Settings for PostgreSQL 17 Multi-Cluster Environment - Mailing list pgsql-admin

From mahamood hussain
Subject Re: Request for Guidance on Recommended ulimit/Open File Settings for PostgreSQL 17 Multi-Cluster Environment
Date
Msg-id CAGc_7H=fZo7TV+uJApkwuMv1+zbTOS+wodZxzTR6YbpH2O-GZQ@mail.gmail.com
Whole thread
In response to Re: Request for Guidance on Recommended ulimit/Open File Settings for PostgreSQL 17 Multi-Cluster Environment  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-admin
Tree view
Thank you for your response. 

How can I determine whether the current setting is sufficient and verify that I’m not hitting any limits with the existing value?


On Tue, May 26, 2026 at 2:33 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Mon, 2026-05-25 at 22:46 +0530, mahamood hussain wrote:
> Current DB2 Setting:
> Max open files = 65535
> We would like clarification on:
>    1. Is increasing the open file limit (ulimit -n) recommended/required for PostgreSQL in such
>       multi-cluster production environments?

65535 will be more than you need, unless you plan to use thousands of partitions or processes,
which is a bad idea anyway.

>    2. What would be the recommended LimitNOFILE value for PostgreSQL considering:multiple clusters
>       on same hostproduction workloadsPgBouncer usageETL-heavy processing

It all depends on how many files (tables, indexes) you plan to use.  If you are worried,
just set the limit higher.

Yours,
Laurenz Albe

pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Request for Guidance on Recommended ulimit/Open File Settings for PostgreSQL 17 Multi-Cluster Environment
Next
From: shammat@gmx.net
Date:
Subject: Collation changes