X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 823D2D1E24D for ; Wed, 12 May 2004 13:52:10 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 07214-04 for ; Wed, 12 May 2004 13:51:49 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 24AB6D1E23E for ; Wed, 12 May 2004 13:51:44 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i4CGpBQx026189; Wed, 12 May 2004 12:51:11 -0400 (EDT) To: "Gordon Ross" Cc: pgsql-admin@postgresql.org Subject: Re: Problems dumping database from 7.3.1 In-reply-to: References: Comments: In-reply-to "Gordon Ross" message dated "Wed, 12 May 2004 15:14:55 +0100" Date: Wed, 12 May 2004 12:51:10 -0400 Message-ID: <26187.1084380670@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/111 X-Sequence-Number: 13427 "Gordon Ross" writes: >> 4. Do whatever it takes in the psql session to provoke crash >> and send along the output of bt. > Program received signal SIGSEGV, Segmentation fault. > 0x806ba0a in nocachegetattr () at eval.c:88 > 88 eval.c: No such file or directory. > (gdb) bt > #0 0x806ba0a in nocachegetattr () at eval.c:88 > #1 0x80d41ec in ExecEvalVar () at eval.c:88 > #2 0x80d549c in ExecEvalExpr () at eval.c:88 > #3 0x80d5809 in ExecTargetList () at eval.c:88 Hmm. The file/line references are obviously wrong, but let's assume that the function names are right (they at least look plausible). What exactly was the query that provoked this? Also, could we see \d output for the table(s) involved? regards, tom lane