Обсуждение: pg_dump and "archive = none" ??

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?

Heiko

--
H. Wilms

Homepage schering.si.uni-hannover.de/hugo
email    wilms@stud.fh-hannover.de

Hi.

There will be no problems, since archiving is no longer supported.
If you want more details, please refer to the documentation about upgrating
to Postgres 6.3

Stoyan Genov

> 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,
Pennsylvania19026