| From: | Sri Mrudula Attili <sri(at)ebi(dot)ac(dot)uk> |
|---|---|
| To: | pgsql-in-general(at)postgresql(dot)org |
| Subject: | Postgresql database terminates abruptly with toomay open files error |
| Date: | 2025-01-14 12:52:34 |
| Message-ID: | 0af98214-3c2a-43e5-9bbf-ddd79b85ea93@ebi.ac.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-in-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sri Mrudula Attili | 2025-01-14 12:58:44 | Postgresql database terminates abruptly with too many open files error |
| Previous Message | Eşref Halıcıoğlu | 2025-01-14 11:00:15 | About PostgreSQL Memory Usage |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sri Mrudula Attili | 2025-01-14 12:58:44 | Postgresql database terminates abruptly with too many open files error |
| Previous Message | Durgamahesh Manne | 2024-10-15 10:14:26 | Re: Inefficient use of index scan on 2nd column of composite index during concurrent activity |