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.94.2)
	(envelope-from <pgsql-in-general-owner+archive@lists.postgresql.org>)
	id 1tXgPP-00Cdfo-Pp
	for pgsql-in-general@arkaria.postgresql.org; Tue, 14 Jan 2025 12:52:41 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-in-general-owner+archive@lists.postgresql.org>)
	id 1tXgPO-000DNP-60
	for pgsql-in-general@arkaria.postgresql.org; Tue, 14 Jan 2025 12:52:38 +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.94.2)
	(envelope-from <sri@ebi.ac.uk>)
	id 1tXgPN-000DNH-Uk
	for pgsql-in-general@lists.postgresql.org; Tue, 14 Jan 2025 12:52:38 +0000
Received: from ironport1.embl.de ([194.94.44.73])
	by magus.postgresql.org with esmtps  (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <sri@ebi.ac.uk>)
	id 1tXgPL-000MCQ-2Q
	for pgsql-in-general@postgresql.org;
	Tue, 14 Jan 2025 12:52:37 +0000
Received: from hl-outgoing01.ebi.ac.uk ([193.62.192.137])
  by ironport1.embl.de with ESMTP; 14 Jan 2025 13:52:34 +0100
Received: from [172.23.50.110] (unknown [172.23.50.110])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	(Authenticated sender: sri)
	by hl-outgoing01.ebi.ac.uk (Postfix) with ESMTPSA id B68233555
	for <pgsql-in-general@postgresql.org>; Tue, 14 Jan 2025 12:52:34 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ebi.ac.uk; s=ebinew;
	t=1736859154; bh=SZTaxR/6auo7am1uxWzounA+bYf7tbBHGI1mp7k9ho8=;
	h=Date:To:From:Subject:From;
	b=mEq5RrHneelBpzfS9/qaVJvHmDiAMgXR67ACizLaxwTI+Oc6mRkWLkbeMiikUSx6S
	 foDunXit69nRJmRR3lEs4VSR6tZhkjPfLbILQ6f/kXl9hvxgL0kKRRBYOb/BL3CnCJ
	 ncHxK0NgGzmROLbHhhNZhtrOP+3YJ8IgUTyf3wFs=
Message-ID: <0af98214-3c2a-43e5-9bbf-ddd79b85ea93@ebi.ac.uk>
Date: Tue, 14 Jan 2025 12:52:34 +0000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: pgsql-in-general@postgresql.org
From: Sri Mrudula Attili <sri@ebi.ac.uk>
Subject: Postgresql database terminates abruptly with toomay open files error
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
List-Id: <pgsql-in-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-in-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-in-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-in-general>
Archived-At: <https://www.postgresql.org/message-id/0af98214-3c2a-43e5-9bbf-ddd79b85ea93%40ebi.ac.uk>
Precedence: bulk

Hello Team,

  We have a postgresql VDB(virtual database- Delphix) that keeps 
terminating due "to too many open files".

Below are few alerts that we could see from the postgresql.log


< 2025-01-14 11:37:20.724 GMT >LOG:  out of file descriptors: Too many 
open files in system; release and retry

< 2025-01-14 11:37:20.724 GMT >FATAL:  epoll_create1 failed: Too many 
open files in system


The number of allowed openfiles at OS level are 65000. even then we see 
these all these being utilised and causing the database to terminate.


Is there a way we could avoid this.


Thanks,

Sri