| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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:27:13 |
| Message-ID: | CAGECzQQ6H6UF+=K_9LryVPaoX2YwiF65jRok-Vgzo1=UEtpUmA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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:
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-12-20 17:31:01 | Re: A few patches to clarify snapshot management |
| Previous Message | Andrey M. Borodin | 2024-12-20 17:16:29 | Re: Sort functions with specialized comparators |