From: | Sri Mrudula Attili <sri(at)ebi(dot)ac(dot)uk> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgresql database terminates abruptly with too many open files error |
Date: | 2025-01-15 11:42:30 |
Message-ID: | 9b69fcc6-dca1-4671-af00-b250f154fb14@ebi.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-in-general |
Hello Tom,
The max_connections =200 and max_files_per_process =1000 as you mentioned.
So should a max_files_per_process =500 helps?
I could see from the number of connections to the databaseis not
exceeding 20. But still these 20 are causing all the damage or using up
all the openfiles quota.
Thanks,
Sri
On 14/01/2025 14:19, Tom Lane wrote:
> Sri Mrudula Attili <sri(at)ebi(dot)ac(dot)uk> writes:
>> We have a postgresql VDB(virtual database- Delphix) that keeps
>> terminating due "to too many open files".
> What do you have max_connections set to, and how many actually-live
> server processes are there typically?
>
>> The number of allowed openfiles at OS level are 65000.
> I'm suspecting that you either need to increase that, decrease
> max_files_per_process (which defaults to 1000), or decrease
> max_connections.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2025-01-15 16:03:33 | Re: Intermittent errors when fetching cursor rows on PostgreSQL 16 |
Previous Message | Enrico Schenone | 2025-01-15 07:46:36 | Re: Intermittent errors when fetching cursor rows on PostgreSQL 16 |
From | Date | Subject | |
---|---|---|---|
Previous Message | Tom Lane | 2025-01-14 14:19:53 | Re: Postgresql database terminates abruptly with too many open files error |