X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 212073A492D for ; Thu, 28 Oct 2004 17:51:00 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 59366-09 for ; Thu, 28 Oct 2004 16:50:57 +0000 (GMT) Received: from ar-sd.net (unknown [82.77.155.72]) by svr1.postgresql.org (Postfix) with ESMTP id 94E863A491C for ; Thu, 28 Oct 2004 17:50:57 +0100 (BST) Received: from localhost (localhost [127.0.0.1]) by ar-sd.net (Postfix) with ESMTP id 41C541FB83; Thu, 28 Oct 2004 19:54:00 +0300 (EEST) Received: from ar-sd.net ([127.0.0.1]) by localhost (linz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04968-04; Thu, 28 Oct 2004 19:53:59 +0300 (EEST) Received: from forge (unknown [192.168.0.11]) by ar-sd.net (Postfix) with SMTP id E306E1FB7B; Thu, 28 Oct 2004 19:53:58 +0300 (EEST) Message-ID: <003101c4bd0e$61108180$0b00a8c0@forge> From: "Andrei Bintintan" To: "Stephan Szabo" Cc: References: <025201c4bcb1$fb556f10$0b00a8c0@forge> <20041027231815.Q66903@megazone.bigpanda.com> Subject: Re: pg_dump doesn't save correct the sequences Date: Thu, 28 Oct 2004 19:51:32 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 X-Virus-Scanned: by amavisd-new at ar-sd.net X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/365 X-Sequence-Number: 15358 Okay, If I modify all the Sequences in the dump, everything works fine. Is there any possibility to specify to the pg_dump to save the sequences with the "old" type??? I mean not with No MAXVALUE and No Minvalue??? My problem is that the 7.3 database I cannot "update" it for the moment for diverse reasons, and I would like not to modify any dump anymore. A strange thing is that this type of dump already worked once.... ----- Original Message ----- From: "Stephan Szabo" To: "Andrei Bintintan" Cc: Sent: Thursday, October 28, 2004 9:22 AM Subject: Re: [ADMIN] pg_dump doesn't save correct the sequences > > On Thu, 28 Oct 2004, Andrei Bintintan wrote: > > > I try to dump a database from a 7.4.2 postgre system and to import it on > > a 7.3.2. system, but I have a problem with the sequences in the dump. > > In general, the above is not guaranteed to work. pg_dump will use features > of the dumping version so moving the dump to an earlier version is filled > with danger. > > > This is a seq example: > > > > CREATE SEQUENCE test_id_seq > > INCREMENT BY 1 > > NO MAXVALUE > > NO MINVALUE > > CACHE 1; > > > > This gives me an error when restoring on the 7.3 machine. > > Looking at the documentation, it looks like NO MAXVALUE and NO MINVALUE > were added in 7.4. > > > I don't know what happened, because last week I also put a dump from 7.4 > > to 7.3 without any problems. > > > A coelege from me made an application and some modifications in the 7.4 > > database system, now I see that in every database there are these tables > > that weren't before: sql_features, sql_implementation_info, > > sql_languages, sql_packages, sql_sizing, sql_sizing_profiles. > > I believe these are part of the SQL standard information_schema. > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend >