Re: seawasp failing, maybe in glibc allocator

Поиск
Список
Период
Сортировка
Искать
От
Fabien COELHO
Тема
Re: seawasp failing, maybe in glibc allocator
Дата
в 21:09:55
Msg-id
alpine.DEB.2.22.394.2105112306480.965029@pseudo
Ответ на
Список
Дерево обсуждения
seawasp failing, maybe in glibc allocator Thomas Munro <thomas.munro@gmail.com>
Re: seawasp failing, maybe in glibc allocator Fabien COELHO <coelho@cri.ensmp.fr>
Re: seawasp failing, maybe in glibc allocator Thomas Munro <thomas.munro@gmail.com>
Re: seawasp failing, maybe in glibc allocator Fabien COELHO <coelho@cri.ensmp.fr>
Re: seawasp failing, maybe in glibc allocator Thomas Munro <thomas.munro@gmail.com>
Re: seawasp failing, maybe in glibc allocator Fabien COELHO <coelho@cri.ensmp.fr>
Re: seawasp failing, maybe in glibc allocator Thomas Munro <thomas.munro@gmail.com>
Re: seawasp failing, maybe in glibc allocator Andres Freund <andres@anarazel.de>
Re: seawasp failing, maybe in glibc allocator Fabien COELHO <coelho@cri.ensmp.fr>
Re: seawasp failing, maybe in glibc allocator Andres Freund <andres@anarazel.de>
Re: seawasp failing, maybe in glibc allocator Fabien COELHO <coelho@cri.ensmp.fr>
Re: seawasp failing, maybe in glibc allocator Fabien COELHO <coelho@cri.ensmp.fr>
Re: seawasp failing, maybe in glibc allocator Fabien COELHO <coelho@cri.ensmp.fr>
Re: seawasp failing, maybe in glibc allocator Thomas Munro <thomas.munro@gmail.com>
Re: seawasp failing, maybe in glibc allocator Fabien COELHO <coelho@cri.ensmp.fr>
Re: seawasp failing, maybe in glibc allocator Thomas Munro <thomas.munro@gmail.com>
Re: seawasp failing, maybe in glibc allocator Andres Freund <andres@anarazel.de>
Re: seawasp failing, maybe in glibc allocator Tom Lane <tgl@sss.pgh.pa.us>
Re: seawasp failing, maybe in glibc allocator Andres Freund <andres@anarazel.de>
Re: seawasp failing, maybe in glibc allocator Andres Freund <andres@anarazel.de>
Re: seawasp failing, maybe in glibc allocator Thomas Munro <thomas.munro@gmail.com>
Re: seawasp failing, maybe in glibc allocator Andres Freund <andres@anarazel.de>
Re: seawasp failing, maybe in glibc allocator Thomas Munro <thomas.munro@gmail.com>
Re: seawasp failing, maybe in glibc allocator Tom Lane <tgl@sss.pgh.pa.us>
Re: seawasp failing, maybe in glibc allocator Andres Freund <andres@anarazel.de>
Re: seawasp failing, maybe in glibc allocator Thomas Munro <thomas.munro@gmail.com>
Re: seawasp failing, maybe in glibc allocator Fabien COELHO <coelho@cri.ensmp.fr>
Re: seawasp failing, maybe in glibc allocator Fabien COELHO <coelho@cri.ensmp.fr>
Re: seawasp failing, maybe in glibc allocator Thomas Munro <thomas.munro@gmail.com>
Re: seawasp failing, maybe in glibc allocator Tom Lane <tgl@sss.pgh.pa.us>
Re: seawasp failing, maybe in glibc allocator Andres Freund <andres@anarazel.de>
Re: seawasp failing, maybe in glibc allocator Thomas Munro <thomas.munro@gmail.com>
Re: seawasp failing, maybe in glibc allocator Fabien COELHO <coelho@cri.ensmp.fr>
Re: seawasp failing, maybe in glibc allocator Andres Freund <andres@anarazel.de>

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.


В списке pgsql-hackers по дате отправления
От: Bruce Momjian
Дата:
От: Bruce Momjian
Дата:
FAQ