Re: Current initdb broken. - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Current initdb broken.
Date
Msg-id 200006111328.JAA04034@candle.pha.pa.us
Whole thread Raw
In response to Re: Current initdb broken.  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Current initdb broken.  (Peter Eisentraut <peter_e@gmx.net>)
Re: Current initdb broken.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
[ Charset ISO-8859-1 unsupported, converting... ]
> Bruce Momjian writes:
> 
> > Well one solution is to have 7.1 use CREATE USER commands, then add the
> > pg_shadow columns in 7.2.
> 
> That's the plan.
> 
> > If we re-order the new columns to be at the end, those columns will load
> > in with NULL's.
> > 
> > We could then modify the user code to make default for NULL values in
> > the new columns.
> 
> 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.

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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: C++ disabled by default
Next
From: Tom Lane
Date:
Subject: Re: ALTER TABLE DROP COLUMN