Re: seawasp failing, maybe in glibc allocator

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: seawasp failing, maybe in glibc allocator
Date: 2021-05-11 21:09:55
Message-ID: alpine.DEB.2.22.394.2105112306480.965029@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Andres,p

>>> Unless perhaps the hard rlimit for -C is set? ulimit -c -H should show
>>> that.
>>
>> Possibly I have just added "ulimit -c unlimited" in the script, we should
>> see the effect on next round.
>
> If it's the hard limit that won't help, because the hard limit can only
> be increased by a privileged process.

It seems to be the soft one, so ISTM that it may work.

Before:

sh> ulimit -c -S
0
sh> ulimit -c -H
unlimited

Then after:

sh> ulimit -c unlimited

I have:

sh> ulimit -c -S
unlimited
sh> ulimit -c -H
unlimited

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2021-05-11 21:11:29 Re: PG 14 release notes, first draft
Previous Message Bruce Momjian 2021-05-11 21:06:03 Re: PG 14 release notes, first draft