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 77A3DD1E275 for ; Wed, 12 May 2004 16:39:24 -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 46783-10 for ; Wed, 12 May 2004 16:39:03 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 67AFAD1B4E6 for ; Wed, 12 May 2004 16:39:01 -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 i4CJZi1n027734; Wed, 12 May 2004 15:35:45 -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 18:24:09 +0100" Date: Wed, 12 May 2004 15:35:44 -0400 Message-ID: <27733.1084390544@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/114 X-Sequence-Number: 13430 "Gordon Ross" writes: > switchboards=# select * from "DNOwner"; > server closed the connection unexpectedly > The DNOwner table is the base table. There are other tables that inherit from this table, and doing a simple select on those produce the same result. Hmm. Does 'select * from only "DNOwner";' work, by any chance? I have a suspicion now that you were bit by the bug repaired in this 7.3.2 bug fix: 2003-01-04 19:56 tgl * src/backend/optimizer/prep/prepunion.c (REL7_3_STABLE): Fix inherited UPDATE for cases where child column numbering doesn't match parent table. This used to work, but was broken in 7.3 by rearrangement of code that handles targetlist sorting. Add a regression test to catch future breakage. What I am thinking happened is that you did an 'UPDATE "DNOwner"' to insert values for the new column, and that because of the aforesaid bug, the updates of the child tables actually corrupted the data (by storing the intended new dnid value into the wrong column position). The crash is probably happening because SELECT is trying to interpret an integer as a text field, or something along that line. If that theory is correct, then the parent table should still be okay (thus the request to try an ONLY select). However, I'm afraid all your child tables are toast, or at least all the rows you updated this way are toast. You could maybe get to a dumpable state by deleting all the child rows, but if the DELETE crashes then you'll have little recourse but to drop the child tables completely. Updating Postgres to 7.3.2 or later will prevent fresh occurrences of the same problem, but unfortunately won't bring back your old data :-(. I hope you have backups ... regards, tom lane