Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id D4637476A2C for ; Thu, 20 Jun 2002 22:39:06 -0400 (EDT) Received: from ashtonwoodshomes.com (unknown [216.94.125.242]) by postgresql.org (Postfix) with ESMTP id 458A6476E1A for ; Thu, 20 Jun 2002 21:33:39 -0400 (EDT) Received: from greatgulfhomes.com. (IDENT:root@[216.191.203.109]) by ashtonwoodshomes.com (8.11.6/8.11.6) with ESMTP id g5L1UPU20197 for ; Thu, 20 Jun 2002 21:30:25 -0400 Received: from terrynew2 (firewall.development.greatgulfhomes.com [216.191.203.106]) by greatgulfhomes.com. (8.11.6/8.11.6) with SMTP id g5L1VQj15187 for ; Thu, 20 Jun 2002 21:31:26 -0400 From: terry@greatgulfhomes.com To: "Postgres (E-mail)" Subject: crash problem Date: Thu, 20 Jun 2002 21:29:31 -0400 Message-ID: <000001c218c3$18736420$2766f30a@development.greatgulfhomes.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Archive-Number: 200206/27 X-Sequence-Number: 1402 My database crashed earlier. It's starts up fine, and I can use it, but I cannot back it up, it reports this error: bash$ pg_dump -t letter_tag_execute_types devtest > bkletter_tag_execute_types getTables(): SELECT (for TRIGGER) failed. Explanation from backend: 'ERROR: No such attribute or function 'tgdeferrable' '. I get the same error if I try to do dumpall. I try looking at the triggers table and this is what I get: devtest=# select * from pg_trigger; ERROR: Relation pg_trigger does not have attribute devtest=# \d pg_trigger Table "pg_trigger" Attribute | Type | Modifier ----------------+------------+---------- tgrelid | oid | tgname | name | tgfoid | oid | tgtype | smallint | tgenabled | boolean | tgisconstraint | boolean | tgconstrname | name | tgconstrrelid | oid | tginitdeferred | boolean | tgnargs | smallint | tgattr | int2vector | tgargs | bytea | Indices: pg_trigger_tgconstrname_index, pg_trigger_tgconstrrelid_index, pg_trigger_tgrelid_index I ran a vacuum, and it did worked, but did not fix this corruption problem. Nothing meaningful appears in the log, just messages about the "backend terminated unexpectedly". What do I do now? I was hoping to upgrade to 7.2.1 this weekend, but if I cannot back it up again, I will loose all of todays work, which was pretty significant, I added much tables and populated a bunch also. Any ideas is appreciated. Thanks Terry Fielder Network Engineer Great Gulf Homes / Ashton Woods Homes terry@greatgulfhomes.com