Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA70654 for ; Sat, 6 Nov 1999 11:45:36 -0500 (EST) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id LAA28567; Sat, 6 Nov 1999 11:45:10 -0500 (EST) From: Bruce Momjian Message-Id: <199911061645.LAA28567@candle.pha.pa.us> Subject: Re: [SQL] pg_dump and "archive = none" ??8 In-Reply-To: <382402CD.3D97A91F@stud.fh-hannover.de> from Heiko Wilms at "Nov 6, 1999 11:28:30 am" To: Heiko Wilms Date: Sat, 6 Nov 1999 11:45:10 -0500 (EST) CC: "pgsql-sql@postgreSQL.org" X-Mailer: ELM [version 2.4ME+ PL65 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Hi, > > I just upgraded from 6.1 to 6.5.2. The databases were saved with pg_dump > before. > When I tried to restore them something went wrong while creating the > tables. The postmaster > complained about "archive = none" after the table definition part in the > dumpfile. It looked like this: > create table foo (var1 text, var2 ....) archive = none; > Even pg_dump -d puts the archive tag in the dumpfile. > So I deleted that and everything went its way. > Testing the database didn't make any trouble but now I wonder if there > might occur a problem > some day because of this a"archive" stuff. > Any idea? Just remove the archive lines. I think they were removed around then. They should have just been ignored by the input routines for a few releases, I guess. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026