Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 06EDB9F9290 for ; Wed, 29 Aug 2007 01:04:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 86230-08 for ; Wed, 29 Aug 2007 01:04:52 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 6F0149F9365 for ; Wed, 29 Aug 2007 01:04:52 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l7T44ohL020668; Wed, 29 Aug 2007 00:04:50 -0400 (EDT) To: KL cc: pgsql-admin@postgresql.org Subject: Re: pg_dump object dump-order; Part II In-reply-to: <46D4E601.4000901@gmx.net> References: <46D4E601.4000901@gmx.net> Comments: In-reply-to KL message dated "Wed, 29 Aug 2007 05:20:33 +0200" Date: Wed, 29 Aug 2007 00:04:49 -0400 Message-ID: <20667.1188360289@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/379 X-Sequence-Number: 26710 KL writes: > Right, the error occurs in exactly such a simple > example, but I'm not above to provide details galore ... This seems to be the relevant detail: > CREATE TABLE event ( > event_id integer DEFAULT nextval('event_id_seq') NOT NULL, This isn't what you showed before --- the previous version had an explicit "::text" cast in it --- and I'm a bit mystified how you managed to get that out of an 8.0.x server. Mine insists on putting ::text in there. [ ... reads further ... ] > NOTE: The SQL-file has been edited as the inserts for table > event have been removed just as the GRANTs/REVOKEs on > scheme PUBLIC. > NOTE 2: Also the MySQL-tool "replace" has been run on > the file to remove the "::text"-typecasts on the > sequence's nextval-statement (to prevent double-casting > in PgSQL 8.1.series the like of "::text)::regclass") Perhaps you need to have a word with whoever is responsible for these NOTEs showing up. Because this sure is not anything any core Postgres developer will answer for. regards, tom lane