Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id CB937B5DC00 for ; Tue, 13 Sep 2011 14:26:05 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 64762-02 for ; Tue, 13 Sep 2011 17:25:59 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 88729B5DC10 for ; Tue, 13 Sep 2011 14:25:59 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p8DHPur4008603; Tue, 13 Sep 2011 13:25:56 -0400 (EDT) To: =?ISO-8859-1?Q?Gunthard_St=FCbs?= cc: pgsql-admin@postgresql.org Subject: Re: exit code 139 performing initdb (pg 9.1 on linux) In-reply-to: <4E6F7ED7.9050000@gmx.de> References: <4E6F7ED7.9050000@gmx.de> Comments: In-reply-to =?ISO-8859-1?Q?Gunthard_St=FCbs?= message dated "Tue, 13 Sep 2011 18:03:35 +0200" Date: Tue, 13 Sep 2011 13:25:56 -0400 Message-ID: <8602.1315934756@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.404 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-0.504 X-Spam-Level: X-Archive-Number: 201109/82 X-Sequence-Number: 38319 =?ISO-8859-1?Q?Gunthard_St=FCbs?= writes: > I installed v9.1 on linux (older suse distr.) from source code using > configure --without-readline (in case that it is important). > performing initdb --locale=de_DE.UTF-8 -D /usr/local/pgsql/data/ everything > run fine until: > vacuuming database template1 ... ok > copying template1 to template0 ... child process exited with exit code 139 > initdb: removing contents of data directory "/usr/local/pgsql/data" Hmm, that's pretty interesting. Exit code 139 is presumably a SIGSEGV, but it's surprising that it would get that far and then crash. Please (1) rebuild with --enable-cassert and --enable-debug configure options, if you didn't already; (2) set "ulimit -c unlimited" if that's not the default in your environment; (3) run initdb with the --noclean option; (4) look into /usr/local/pgsql/data to find the core file left behind by the crash, and do $ gdb /usr/local/bin/postgres /path/to/core-file gdb> bt gdb> quit (5) post the output of "bt" here. BTW, what compiler version are you using exactly, and what compiler options? regards, tom lane