Re: Current initdb broken.

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
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 11:41:09
Message-ID: Pine.LNX.4.21.0006102146400.9195-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-06-11 11:41:24 Re: Adding time to DATE type
Previous Message Tom Lane 2000-06-11 03:41:51 Re: Current initdb broken.