| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk>, hackers(at)postgresql(dot)org |
| Subject: | Re: Current initdb broken. |
| Date: | 2000-06-11 13:28:08 |
| Message-ID: | 200006111328.JAA04034@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-11 16:22:42 | Re: ALTER TABLE DROP COLUMN |
| Previous Message | Peter Eisentraut | 2000-06-11 11:46:57 | C++ disabled by default |