From: | jade <jade(at)vanzoest(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-sql(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [SQL] postgresql 7.1 file descriptor |
Date: | 2002-05-09 06:18:17 |
Message-ID: | 20020508230403.H81883-100000@vision.estjohn.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
On Wed, 8 May 2002, Tom Lane wrote:
> jade <jade(at)vanzoest(dot)com> 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).
Hi All,
Thanks for all the response -- it was all very helpful! I don't want to limit
the my backend processes because each response is consider "important" so
running any backend limitation is consider unaccceptable. So, I've increased
the system NFIle limit.. so far so good :-)
Are they any way to pool connections through a single backend process?
thanks,
Thanh
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2002-05-09 07:12:04 | Re: OK, lets talk portability. |
Previous Message | Tom Lane | 2002-05-09 05:28:10 | Re: Regression tests and NOTICE statements |
From | Date | Subject | |
---|---|---|---|
Next Message | Curt Sampson | 2002-05-09 07:11:59 | Re: Performance issues with compaq server |
Previous Message | Rajesh Kumar Mallah. | 2002-05-09 05:21:17 | Re: psql: question |