Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wRcSD-002WQf-0N for pgsql-admin@arkaria.postgresql.org; Mon, 25 May 2026 21:03:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wRcSB-0024qe-0W for pgsql-admin@arkaria.postgresql.org; Mon, 25 May 2026 21:03:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wRcSA-0024qW-2c for pgsql-admin@lists.postgresql.org; Mon, 25 May 2026 21:03:15 +0000 Received: from mail-wr1-x42a.google.com ([2a00:1450:4864:20::42a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wRcS9-00000001PZ2-30Gy for pgsql-admin@lists.postgresql.org; Mon, 25 May 2026 21:03:15 +0000 Received: by mail-wr1-x42a.google.com with SMTP id ffacd0b85a97d-44ccbd3290aso8676138f8f.2 for ; Mon, 25 May 2026 14:03:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1779742992; x=1780347792; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=hSQBfeYq+rTVwWyaFQ8ZrQZMVnzq1ezdou9bc9g3rek=; b=QRx/UJP56sScBCOwmYakHzw8FZ/K2/1qefI3wyMSK19p78cRLuuxiweE2vWNCUzL7J MMDsoaZB2bZ3Kwc5OqfVhXyqcUsqlJ7/PbIREU6/YHXoTtTuaaneIa2u02m/aG6fdxlp aqrh+HGKwBr5eUVSh7S6vkEWosUoaXBkFt38nPqXtdUv2+HHSZKJj/lFimHeHzRYe9tV w6hzEgBg2c6JAvgHcrmwFVutEC3lbCIOT179N8FK+RsbxXeZfU78R099x1OmMTJwnrch K4JmLlT/XgefcvH04LcHySDX7RYp/k55f0RvAwOdFTZE/6dA/aGKgjb6m3XnU1tmFPbY wQ8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1779742992; x=1780347792; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=hSQBfeYq+rTVwWyaFQ8ZrQZMVnzq1ezdou9bc9g3rek=; b=gLcCnBH5RTV37LogOksMCFa9GGWDm6/7dfnfur95S3W5gPXfvkqgHkMIv4IuOlA2CJ dgDzJsr8Qgqv2mlHJhCyBsL2fJiJK5WqdtL292dy6SiELlvrl9ZsNgxhtzn4RLS0IdZa ZueQkjhH5d5kvI42BPDMaLMLvshMQQPrqaQJASnkDV4pCV4664MiPX6qxEt5oEKnzCh/ x1NV/FLoYLEoUrBz4rcovK7my3VPos9lW5roeX6ZvbFWLVSZ5CfIPUeGFJwD6ZU/DWt/ 3Y5bBrPwB6V7Ofc35L4QLuWk5zAU1eG+iKHj0LzbTtZwB6jH/zuolZpZu6kDRG+/y8yi q+kQ== X-Forwarded-Encrypted: i=1; AFNElJ+KF5xkbD0R/4mc57yFtUCWS/mWGICAZGlGFn5xpuQAc5zSLeJoVraw7IPqwBUAyWT7lg5eQItOhDMdcw==@lists.postgresql.org X-Gm-Message-State: AOJu0Yx7844FDDuseBMWT95UO8xOe+g6a5CdaFrgbhUCCSJhfpDHPi0N GI05N1CoTSFZiIwcOY5akSTXxO9q9ACN7zXJ9rkMbegaUxA8O9BOx6OJ6wpr6gnNNbdLl37V52v 3Zw3s X-Gm-Gg: Acq92OGE3ccUUpcb7qh3VI7m/tkuwJsPh3oj+aZJvCa8kMEkndwKMZK9/qZ1A0PatV/ DcQBexEfWvhHDZSLGgqtoOlDzE4pQQbMBIjAphP3Rcdm3u43xMNF1sYqhaZ/yjRZTm00UQLmAX8 fZv/ObzWeZlSuzcTIaNYC+MoEsahd4R1I5brx9uC0LWjIQtNbodjjBv91wDblqRmlDZ184rXoEg CODJqhVBTFYN54fHy966uFYdzPVvJu1o1PTl3FYg+YBhv+fbgULFihhnvoY4PgCybkw+32p81EH lEgscGXUJACUBeC93VF2YNNSWuSvilj5QREKjThwesWu++5SAaMqLOLNHdMUUaYhNKak/LOGxqn fjGRavTRYqcU0nbWMd4wGN41+atc1Wa+hGmK1CeLfDrjCjMtsVEktX5ykdnIPshh2nG75LoRk+H EsHajA9FlXo/n8pys3+wyQ4iJ0d5qE/v/QFiWL2ooN+xMGeBkY8JzrCw== X-Received: by 2002:a05:6000:25e1:b0:43d:77f4:7145 with SMTP id ffacd0b85a97d-45eb389d3e1mr28603561f8f.19.1779742991713; Mon, 25 May 2026 14:03:11 -0700 (PDT) Received: from laurenz.albe-K4N0CV00F97414D ([2001:871:260:b47a:8557:232e:e3f6:d2b3]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-45eb6d5e363sm30649200f8f.28.2026.05.25.14.03.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 25 May 2026 14:03:11 -0700 (PDT) Message-ID: Subject: Re: Request for Guidance on Recommended ulimit/Open File Settings for PostgreSQL 17 Multi-Cluster Environment From: Laurenz Albe To: mahamood hussain , Pgsql-admin Date: Mon, 25 May 2026 23:03:09 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 2026-05-25 at 22:46 +0530, mahamood hussain wrote: > Current DB2 Setting: > Max open files =3D 65535 > We would like clarification on: > =C2=A0=C2=A0=C2=A01. Is increasing the open file limit (ulimit -n) recomm= ended/required for PostgreSQL in such > multi-cluster production environments? 65535 will be more than you need, unless you plan to use thousands of parti= tions or processes, which is a bad idea anyway. > =C2=A0=C2=A0=C2=A02. 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