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

From: mahamood hussain <hussain(dot)ieg(at)gmail(dot)com>
To: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Request for Guidance on Recommended ulimit/Open File Settings for PostgreSQL 17 Multi-Cluster Environment
Date: 2026-05-26 05:36:53
Message-ID: CAGc_7H=fZo7TV+uJApkwuMv1+zbTOS+wodZxzTR6YbpH2O-GZQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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(dot)albe(at)cybertec(dot)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
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Laurenz Albe 2026-05-26 07:57:26 Re: Request for Guidance on Recommended ulimit/Open File Settings for PostgreSQL 17 Multi-Cluster Environment
Previous Message Laurenz Albe 2026-05-25 21:03:09 Re: Request for Guidance on Recommended ulimit/Open File Settings for PostgreSQL 17 Multi-Cluster Environment