Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id F226B2E0031 for ; Mon, 14 Apr 2008 10:32:37 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 83640-07 for ; Mon, 14 Apr 2008 10:32:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id A58B42E002F for ; Mon, 14 Apr 2008 10:32:31 -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 m3EDWSij001072; Mon, 14 Apr 2008 09:32:28 -0400 (EDT) To: Darren Reed cc: pgsql-admin@postgresql.org Subject: Re: postgres 8.2.6 core dump when initialising. In-reply-to: <4802F108.2090709@fastmail.net> References: <4802F108.2090709@fastmail.net> Comments: In-reply-to Darren Reed message dated "Sun, 13 Apr 2008 22:52:08 -0700" Date: Mon, 14 Apr 2008 09:32:28 -0400 Message-ID: <1071.1208179948@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/116 X-Sequence-Number: 28880 Darren Reed writes: > Program terminated with signal 11, Segmentation fault. > #0 0x0829845c in RelationCacheInitializePhase2 () at relcache.c:2400 > 2400 LOAD_CRIT_INDEX(TriggerRelidNameIndexId); > (gdb) where > #0 0x0829845c in RelationCacheInitializePhase2 () at relcache.c:2400 This appears to be the exact same problem you reported back in February: http://archives.postgresql.org/pgsql-admin/2008-02/msg00370.php I'm thinking there must be something about what you are doing that is triggering this issue. Care to give us a full data dump on your maintenance habits? It might be useful if we could look at a pg_filedump dump of your pg_class table, too. http://sources.redhat.com/rhdb/ regards, tom lane