Re: Postgresql database terminates abruptly with too many open files error - Mailing list pgsql-general

From Durgamahesh Manne
Subject Re: Postgresql database terminates abruptly with too many open files error
Date
Msg-id CAJCZkoLT_9iL+C9iMP+C6-7Fha0uy4UN5c6vNZPRoKs-+G8viQ@mail.gmail.com
Whole thread Raw
In response to Re: Postgresql database terminates abruptly with too many open files error  (Sri Mrudula Attili <sri@ebi.ac.uk>)
List pgsql-general


---------- Forwarded message ---------
From: Sri Mrudula Attili <sri@ebi.ac.uk>
Date: Wed, 15 Jan, 2025, 17:12
Subject: Re: Postgresql database terminates abruptly with too many open files error
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: <pgsql-general@postgresql.org>


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@ebi.ac.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


Hi Team,

What is the final conclusion for this ?

Regards,
Durga Mahesh 


pgsql-general by date:

Previous
From: Jeremy Schneider
Date:
Subject: Re: glibc 2.35-2.39 upgrade requirements
Next
From:
Date:
Subject: RE: pg_repack and locks