Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id B7E78477774; Thu, 7 Nov 2002 10:10:59 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 0FE934776C3; Thu, 7 Nov 2002 09:55:50 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id gA7EtUhR019209; Thu, 7 Nov 2002 09:55:30 -0500 (EST) To: Achilleus Mantzios Cc: Stephan Szabo , pgsql-sql@postgresql.org, pgsql-general@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [SQL] Problem: Referential Integrity Constraints lost In-reply-to: References: Comments: In-reply-to Achilleus Mantzios message dated "Thu, 07 Nov 2002 09:57:20 +0200" Date: Thu, 07 Nov 2002 09:55:29 -0500 Message-ID: <19207.1036680929@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/265 X-Sequence-Number: 32686 Achilleus Mantzios writes: > After recreating the missing triggers should i upgrade > to 7.2.3?? Make that "before". I frankly suspect pilot error here. Triggers do not simply disappear. If you did have crash-induced corruption leading to loss of some rows in pg_trigger, it would be exceedingly obvious because *no* operations on the affected tables would work --- relcache would complain about the fact that pg_class.reltriggers didn't match the number of rows in pg_trigger. I think the missing triggers must have been removed or disabled deliberately. (Which is not to say that it couldn't have been a software bug, but you're barking up the wrong tree to blame it on a crash.) Did all the triggers of the affected tables disappear, or only some of them? regards, tom lane