Stephen Frost <sfrost@snowman.net> writes:
> On Tue, May 17, 2022 at 18:12 Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> ulimit might be interesting to check into as well. The last time I
>> looked, it wasn't too helpful for this on Linux, but that was years ago.
> Unfortunately I really don’t think anything here has materially changed in
> a way which would help us. This would also apply across all of PG’s
> processes and I would think it’d be nice to differentiate between user
> backends running away and sucking up a ton of memory vs backend processes
> that shouldn’t be constrained in this way.
It may well be that they've not fixed its shortcomings, but the claim
that it couldn't be applied selectively is nonsense. See setrlimit(2),
which we already use successfully (AFAIK) to set stack space on a
per-process basis.
regards, tom lane
