Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id A5C8B476350; Wed, 8 May 2002 13:41:36 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 99D1E476165; Wed, 8 May 2002 12:32:30 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g48GVkW02955; Wed, 8 May 2002 12:31:46 -0400 (EDT) To: jade Cc: pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: postgresql 7.1 file descriptor In-reply-to: <20020507152551.M65365-100000@vision.estjohn.com> References: <20020507152551.M65365-100000@vision.estjohn.com> Comments: In-reply-to jade message dated "Tue, 07 May 2002 15:36:30 -0700" Date: Wed, 08 May 2002 12:31:46 -0400 Message-ID: <2952.1020875506@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200205/360 X-Sequence-Number: 22567 jade writes: > I am running postgresql - 7.1 on Redhat 2.2.16-22 kernel. > Sometimes this the system becomes totally unusable with > "VFS: file-max limit 4096 reached" error? The system is setup to have > 4096 file descriptor as default. I was wondering how many file descriptor > does postgres open per backend process? Potentially lots. Increase your system's NFILE limit, or reduce the max number of backends you will allow PG to start, or update to 7.2 which will let you set a per-backend file limit (see MAX_FILES_PER_PROCESS; AFAIR that parameter did not exist in 7.1). regards, tom lane