Re: [HACKERS] Assignment of valid collation for SET operations onqueries with UNKNOWN types.

Поиск
Список
Период
Сортировка
От Rahila Syed
Тема Re: [HACKERS] Assignment of valid collation for SET operations onqueries with UNKNOWN types.
Дата
Msg-id CAH2L28tKV9pbR2=NuX4k5O=pXCzVhB9Xx2=OXUk8bbqHMC1=1g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Assignment of valid collation for SET operations on queries with UNKNOWN types.  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: [HACKERS] Assignment of valid collation for SET operations onqueries with UNKNOWN types.  (Michael Paquier <michael.paquier@gmail.com>)
Re: [HACKERS] Assignment of valid collation for SET operations onqueries with UNKNOWN types.  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
Список pgsql-hackers
Hello,

Thank you for comments.

>There is a similar code pattern for materialized views, see
>create_ctas_nodata() where the attribute list is built
create_ctas_nodata() is for creation of materialized views WITH NO DATA.
For other materialized views and CREATE TABLE AS, column definitions are built in
intorel_startup() function which has different code from that of CREATE VIEW which
the patch deals with.

Limiting the scope of the patch to include changing the type of literal constants
to text only for plain views. Also, error out when column with UNKNOWN type is
being created for other relations like tables and materialized views.

>And actually, shouldn't this be just a plain error?
Changed it to error in the attached patch.

>Your patch has no regression tests, surely you want some to stress
>this code path
Added regression tests in the attached patch.

Also adding this patch to CF 2017-01

Thank you,
Rahila Syed


Вложения

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

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: [HACKERS] Hash Indexes
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: [HACKERS] Assignment of valid collation for SET operations onqueries with UNKNOWN types.