Re: InitDB: Bad system call

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Torsten Zühlsdorff <foo(at)meisterderspiele(dot)de>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: InitDB: Bad system call
Date: 2010-08-11 16:31:51
Message-ID: 7538.1281544311@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Torsten Zhlsdorff's message of mi ago 11 02:52:34 -0400 2010:
>>>> Bad system call (core dumped)

> I think you should try harder to generate the core file. Maybe you have
> too low an "ulimit -c" setting?

The kernel message indicates that core *is* being dumped. Possibly it's
being dumped in the $PGDATA directory, which initdb will rm -rf on
failure. Try using initdb --noclean.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2010-08-11 16:42:01 Re: pgtune
Previous Message Merlin Moncure 2010-08-11 16:24:35 Re: How-to question: pre-parsing and pre-planning dynamic sql statements