Re: seawasp failing, maybe in glibc allocator - Mailing list pgsql-hackers

From Andres Freund
Subject Re: seawasp failing, maybe in glibc allocator
Date
Msg-id 20210511171342.4fgskmhwglnjbc7i@alap3.anarazel.de
Whole thread Raw
In response to Re: seawasp failing, maybe in glibc allocator  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: seawasp failing, maybe in glibc allocator
List pgsql-hackers
On 2021-05-11 10:22:02 +0200, Fabien COELHO wrote:
> 
> > On 2021-05-11 12:16:44 +1200, Thomas Munro wrote:
> > > OK we got the SIGABRT this time, but still no backtrace.  If the
> > > kernel's core_pattern is "core", gdb is installed, then considering
> > > that the buildfarm core_file_glob is "core*" and the script version is
> > > recent (REL_12), then I'm out of ideas.  ulimit -c XXX shouldn't be
> > > needed because the perl script does that with rlimit.
> > 
> > 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.



pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: PG 14 release notes, first draft
Next
From: Andres Freund
Date:
Subject: Re: Performance degradation of REFRESH MATERIALIZED VIEW