Re: Current initdb broken.

Поиск
Список
Период
Сортировка
Искать
От
Peter Eisentraut
Тема
Re: Current initdb broken.
Дата
Msg-id
Pine.LNX.4.21.0006120018500.353-100000@localhost.localdomain
Ответ на
Re: Current initdb broken. (Bruce Momjian)
Список
Дерево обсуждения
Current initdb broken. Keith Parks <emkxp01@mtcc.demon.co.uk>
Re: Current initdb broken. Bruce Momjian <pgman@candle.pha.pa.us>
Re: Current initdb broken. Peter Eisentraut <peter_e@gmx.net>
Re: Current initdb broken. Bruce Momjian <pgman@candle.pha.pa.us>
Re: Current initdb broken. Peter Eisentraut <peter_e@gmx.net>
Re: Current initdb broken. Bruce Momjian <pgman@candle.pha.pa.us>
Re: Current initdb broken. Tom Lane <tgl@sss.pgh.pa.us>
Re: Current initdb broken. Peter Eisentraut <peter_e@gmx.net>
Re: Current initdb broken. Bruce Momjian <pgman@candle.pha.pa.us>
Re: Current initdb broken. Bruce Momjian <pgman@candle.pha.pa.us>
Re: Current initdb broken. Tom Lane <tgl@sss.pgh.pa.us> 
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.

-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden
В списке pgsql-hackers по дате отправления
Предыдущее
От: Peter Eisentraut
Дата:
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: Install error current CVS
FAQ