Re: [HACKERS] pg_dumpall

>
>
> 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...

Yikes, we never changed pg_user to pg_shadow in pg_dumpall. Isn't that
the real problem. Need to have that patched, or people will not be able
to upgrade. Applying patch now.

Do I put this patch in the patches directory?

--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)