| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, 陈宗志 <baotiao(at)gmail(dot)com> |
| Subject: | Re: AIO v2.0 |
| Date: | 2024-12-20 17:39:33 |
| Message-ID: | s2suzn6rppv7hxxayvlk2wvxlwqa4slzzrxlw5kx7j44txhe7r@4lbgr6aanyp2 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2024-12-20 18:27:13 +0100, Jelte Fennema-Nio wrote:
> On Fri, 20 Dec 2024 at 01:54, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > Arguably the configuration *did* tell us, by having a higher hard limit...
> > <snip>
> > But opting into a higher rlimit, while obviously adhering to the hard limit
> > and perhaps some other config knob, seems fine?
>
> Yes, totally fine. That's exactly the reasoning why the hard limit is
> so much larger than the soft limit by default on systems with systemd:
>
> https://0pointer.net/blog/file-descriptor-limits.html
Good link.
This isn't just relevant for using io_uring:
There obviously are several people working on threaded postgres. Even if we
didn't duplicate fd.c file descriptors between threads (we probably will, at
least initially), the client connection FDs alone will mean that we have a lot
more FDs open. Due to the select() issue the soft limit won't be increased
beyond 1024, requiring everyone to add a 'ulimit -n $somehighnumber' before
starting postgres on linux doesn't help anyone.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trey Boudreau | 2024-12-20 18:56:20 | Discussion on a LISTEN-ALL syntax |
| Previous Message | Heikki Linnakangas | 2024-12-20 17:31:01 | Re: A few patches to clarify snapshot management |