| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sri Mrudula Attili <sri(at)ebi(dot)ac(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgresql database terminates abruptly with too many open files error |
| Date: | 2025-01-14 14:19:53 |
| Message-ID: | 679341.1736864393@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-in-general |
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-14 17:56:33 | Re: Intermittent errors when fetching cursor rows on PostgreSQL 16 |
| Previous Message | Ron Johnson | 2025-01-14 13:39:27 | Re: Postgresql database terminates abruptly with too many open files error |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sri Mrudula Attili | 2025-01-15 11:42:30 | Re: Postgresql database terminates abruptly with too many open files error |
| Previous Message | Ron Johnson | 2025-01-14 13:39:27 | Re: Postgresql database terminates abruptly with too many open files error |