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 ED588D1E232 for ; Wed, 12 May 2004 17:21:54 -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 60475-09 for ; Wed, 12 May 2004 17:21:36 -0300 (ADT) Received: from host4.ccw.gov.uk (host4.ccw.gov.uk [62.3.229.112]) by svr1.postgresql.org (Postfix) with ESMTP id 5A728D1E27E for ; Wed, 12 May 2004 17:21:33 -0300 (ADT) Received: from host3.ccw.gov.uk ([192.168.253.7] helo=host3.hq.ccw.gov.uk) by host4.ccw.gov.uk with esmtp (Exim 4.20) id 1BNzy9-0003Du-6D for pgsql-admin@postgresql.org; Wed, 12 May 2004 21:04:45 +0100 Received: from groupwise.ccw.gov.uk ([192.168.24.30]) by host3.hq.ccw.gov.uk with esmtp (Exim 4.14) id 1BO0VX-0003xy-C1 for pgsql-admin@postgresql.org; Wed, 12 May 2004 21:39:15 +0100 Received: from CCW_Gateways-MTA by groupwise.ccw.gov.uk with Novell_GroupWise; Wed, 12 May 2004 21:20:59 +0100 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Date: Wed, 12 May 2004 21:20:51 +0100 From: "Gordon Ross" To: Subject: Re: Problems dumping database from 7.3.1 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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/116 X-Sequence-Number: 13432 *SIGH* Oh, well. I suppose I should have updated up development machine a w= hile ago. ./configure; make here we come. Thank you for looking at this. At least I can be re-assured that the proble= m is fixed in later versions of Postgres. GTG >>> Tom Lane 05/12/04 20:36 PM >>> "Gordon Ross" writes: > switchboards=3D# 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