Re: BUG #5736: 9.0.1 segmentation fault (sig11) during long-lived update

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #5736: 9.0.1 segmentation fault (sig11) during long-lived update
Дата
Msg-id 23040.1288471381@sss.pgh.pa.us
обсуждение исходный текст
Ответ на BUG #5736: 9.0.1 segmentation fault (sig11) during long-lived update  ("Henry" <henka@cityweb.co.za>)
Ответы Re: BUG #5736: 9.0.1 segmentation fault (sig11) during long-lived update
Re: BUG #5736: 9.0.1 segmentation fault (sig11) during long-lived update
Список pgsql-bugs
"Henry" <henka@cityweb.co.za> writes:
> Before I run this again, what's the best way to proceed to get a core dump
> so I can run a gdb backtrace to provide more info?  Simply 'ulimit -c
> 5242880' as user postgres and restart PG?

I'd use "ulimit -c unlimited", myself, rather than making arbitrary
assumptions about how big the corefile might be.

Also, make sure the ulimit command is effective in the shell that will
actually launch the postmaster.  This can be tricky if your PG launch
script uses "su".  If you're using the RH or PGDG RPMs' initscript,
I'd suggest putting the ulimit command in ~postgres/.bash_profile.

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Greg Stark
Дата:
Сообщение: Re: BUG #5732: parsing of: "WHERE mycol=123AND ..."
Следующее
От: Arturas Mazeika
Дата:
Сообщение: Re: BUG #5735: pg_upgrade thinks that it did not start the old server