From: | Rahila Syed <rahilasyed90(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Assignment of valid collation for SET operations on queries with UNKNOWN types. |
Date: | 2016-12-14 10:02:34 |
Message-ID: | CAH2L28tKV9pbR2=NuX4k5O=pXCzVhB9Xx2=OXUk8bbqHMC1=1g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
Attachment | Content-Type | Size |
---|---|---|
unknown_view_column_to_text_v1.patch | application/x-download | 3.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-12-14 10:09:36 | Re: Assignment of valid collation for SET operations on queries with UNKNOWN types. |
Previous Message | Amit Kapila | 2016-12-14 09:27:40 | Re: Hash Indexes |