Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3AF552E0040 for ; Wed, 27 Feb 2008 01:13:54 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 25777-04 for ; Wed, 27 Feb 2008 01:13:51 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by postgresql.org (Postfix) with ESMTP id 01D512E0064 for ; Wed, 27 Feb 2008 01:13:51 -0400 (AST) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 3866DA2966; Wed, 27 Feb 2008 00:13:51 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 27 Feb 2008 00:13:51 -0500 X-Sasl-enc: qjv8+jrs55kVd3x+dQIEGya9GlK93Rtl1bS0OPmybj9A 1204089230 Received: from [192.168.1.235] (76-191-150-176.dsl.dynamic.sonic.net [76.191.150.176]) by mail.messagingengine.com (Postfix) with ESMTPSA id B55C5205D3; Wed, 27 Feb 2008 00:13:49 -0500 (EST) Message-ID: <47C4F178.1050102@fastmail.net> Date: Tue, 26 Feb 2008 21:13:28 -0800 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Tom Lane CC: Shoaib Mir , pgsql-admin@postgresql.org Subject: Re: How to reindex when unable to open relation? References: <47C3AE1F.2010804@fastmail.net> <47C3E88B.8070803@fastmail.net> <2862.1204040458@sss.pgh.pa.us> In-Reply-To: <2862.1204040458@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200802/358 X-Sequence-Number: 28432 Tom Lane wrote: > Darren Reed writes: > > Hmmm, from the logfile, signal 11, so it core dumped... > > Of course the default built binary is -O2... > > (gdb) where > > #0 0x082114b8 in RelationCacheInitializePhase2 () > > #1 0x0821fa67 in InitPostgres () > > #2 0x081a7d8b in PostgresMain () > > #3 0x08184882 in ServerLoop () > > #4 0x0818545c in PostmasterMain () > > #5 0x0814be1f in main () > > Hm, if you are really lucky, this is because of a corrupt > pg_internal.init file. Fortunately for you, that's just a cache; > try removing (all of the) pg_internal.init files and see if the > DB will start. > How do I know which files those are? I see nothing named that although grep suggests they did exist... # grep pg_internal.init */* Binary file base/1 matches Binary file base/10818 matches Binary file base/10819 matches Darren