| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | t(dot)katsumata1122(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #8542: Materialized View with another column_name does not work? |
| Date: | 2013-10-21 10:02:23 |
| Message-ID: | CAB7nPqR9OZmiDgCnJOugO+UoW3gg1+gk5CfSDZ5OLUGJTRr6kg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Mon, Oct 21, 2013 at 6:41 PM, <t(dot)katsumata1122(at)gmail(dot)com> wrote:
> - Creating materialized view with column_name
> CREATE MATERIALIZED VIEW mv_t(ii) AS SELECT * FROM t;
> And then, I got a bellow ERROR.
> ----
> ERROR: SELECT rule's target entry 1 has different column name from "ii"
> Is this a bug or restriction for Materialized View?
Looks like a bug as documentation is clear here: "If column names are
not provided, they are taken from the output column names of the
query".
http://www.postgresql.org/docs/9.3/static/sql-creatematerializedview.html
In your case you are providing the column names, so they should be
used for this matview.
Regards,
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomonari Katsumata | 2013-10-21 10:44:57 | Re: BUG #8542: Materialized View with another column_name does not work? |
| Previous Message | t.katsumata1122 | 2013-10-21 09:41:17 | BUG #8542: Materialized View with another column_name does not work? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KONDO Mitsumasa | 2013-10-21 10:27:26 | Re: [HACKERS] Who is pgFoundery administrator? |
| Previous Message | t.katsumata1122 | 2013-10-21 09:41:17 | BUG #8542: Materialized View with another column_name does not work? |