Re: BUG #15247: At 'ALTER TABLE ADD COLUMN fast default' , Set attmissingval to NULL in the pg_attribute, query fail

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #15247: At 'ALTER TABLE ADD COLUMN fast default' , Set attmissingval to NULL in the pg_attribute, query fail
Дата
Msg-id 10837.1529418216@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #15247: At 'ALTER TABLE ADD COLUMN fast default' , Set attmissingval to NULL in the pg_attribute, query fail  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Список pgsql-bugs
Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
> "PG" == PG Bug reporting form <noreply@postgresql.org> writes:
>  PG> (4)  update pg_attribute set attmissingval = NULL where attname = 'b';

> Nobody ever claimed that you could update pg_attribute without crashing
> the server; I can think of half a dozen ways to do it.

Specifically, you broke it by not keeping atthasmissing consistent with
attmissingval.  Manually corrupting catalogs like that is not a supported
operation.

            regards, tom lane


В списке pgsql-bugs по дате отправления:

Предыдущее
От: Steven Winfield
Дата:
Сообщение: RE: BUG #15248: pg_upgrade fails when a function with an emptysearch_path is encountered
Следующее
От: Robert Haas
Дата:
Сообщение: Re: row_to_json(), NULL values, and AS