Re: Current initdb broken.

[ Charset ISO-8859-1 unsupported, converting... ]
> Bruce Momjian writes:
> 
> > > I'm not sure, that would break the basic line of error checking in COPY.
> > 
> > It would be active only for pg_shadow and no other table.  However, I
> > see that having not enough column in COPY fills the rest with NULL and
> > does not report an error.
> 
> The problem remains that this change is conceptually questionable in the
> first place.
> 

OK, I have backed out the changes.  We can always use them later if we
wish.

--  Bruce Momjian                        |  http://www.op.net/~candle pgman@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