Re: BUG #15579: Adding a column with default from configurationparameter fails on 11.1

Поиск
Список
Период
Сортировка
От Dmitry Dolgov
Тема Re: BUG #15579: Adding a column with default from configurationparameter fails on 11.1
Дата
Msg-id CA+q6zcUHseOR7YGhoTn8Df_HBGUP4jfgmWuCB2vixhtU0=7phQ@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #15579: Adding a column with default from configuration parameterfails on 11.1  (PG Bug reporting form <noreply@postgresql.org>)
Список pgsql-bugs
Дерево обсуждения 
> On Mon, Jan 7, 2019 at 1:33 PM PG Bug reporting form <noreply@postgresql.org> wrote:
>
> Is this a bug or pehaps an intended change? We tried googling but
> didn't find anything which seemed relevant.

Well, I guess it was introduced here [1] for fast ALTER TABLE ADD COLUMN
feature:

    The default expression is evaluated at the time of the ALTER TABLE and the
    result stored in a new column (attmissingval) in pg_attribute

Although I wonder if this case with current_setting was taken into account.
Probably it doesn't make sense to use fast alter table if a table is empty.


[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=16828d5c0273b4fe5f10f42588005f16b415b2d8

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

Предыдущее
От: Bartosz Polnik
Дата:
Сообщение: Re: BUG #15577: Query returns different results when executedmultiple times
Следующее
От: a Marath
Дата:
Сообщение: Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name