pg_dumpall

From: Andrew Martin <martin(at)biochemistry(dot)ucl(dot)ac(dot)uk>
To: pgsql-hackers(at)postgresql(dot)org
Subject: pg_dumpall
Date: 1998-03-06 16:45:15
Message-ID: 199803061645.QAA19269@bsmir06.biochem.ucl.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


I've dumped a 6.1 database using the pg_dumpall from 6.3 to load into
6.3.

The format of the data to be copied into pg_user is wrong - there are
not enough columns. I guess this may be a problem from having skipped
out 6.2, but it would be nice if it worked properly :-)

Also one of the column names I had used in my old database is no longer
allowed ('local'). Again, it would be nice if pg_dumpall could spot
no-longer allowed column names and warn the user rather than having
psql crash when one tries to import the data and then having to trace
back to where the problem was...

Best wishes,

Andrew
----------------------------------------------------------------------------
Dr. Andrew C.R. Martin University College London
EMAIL: (Work) martin(at)biochem(dot)ucl(dot)ac(dot)uk (Home) andrew(at)stagleys(dot)demon(dot)co(dot)uk
URL: http://www.biochem.ucl.ac.uk/~martin
Tel: (Work) +44(0)171 419 3890 (Home) +44(0)1372 275775

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shiby Thomas 1998-03-06 17:01:59 Re: [HACKERS] Execution time
Previous Message Maurice Gittens 1998-03-06 15:30:56 newoid in invapi.c