Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 48FC1475C48 for ; Thu, 7 Mar 2002 17:24:47 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g27MOmS15597; Thu, 7 Mar 2002 17:24:48 -0500 (EST) To: gry@ll.mit.edu Cc: pgsql-sql@postgresql.org Subject: Re: Fw: Re: 7.0.3 pg_dump -> segmentation fault! In-reply-to: <20020307154431.769de3d8.gry@ll.mit.edu> References: <20020307154431.769de3d8.gry@ll.mit.edu> Comments: In-reply-to george young message dated "Thu, 07 Mar 2002 15:44:31 -0500" Date: Thu, 07 Mar 2002 17:24:48 -0500 Message-ID: <15594.1015539888@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200203/93 X-Sequence-Number: 6974 george young writes: > In fact, anything I try to do to runs_tmp I get the same above error, select, delete, drop... > This table is not important and if I could blow it and the trigger away, that would be great. If nothing else works, delete the pg_class row for the table; then you should be able to pg_dump. regards, tom lane