Re: BUG #8542: Materialized View with another column_name does not work? - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #8542: Materialized View with another column_name does not work?
Date
Msg-id CAB7nPqR9OZmiDgCnJOugO+UoW3gg1+gk5CfSDZ5OLUGJTRr6kg@mail.gmail.com
Whole thread Raw
In response to BUG #8542: Materialized View with another column_name does not work?  (t.katsumata1122@gmail.com)
Responses Re: BUG #8542: Materialized View with another column_name does not work?
List pgsql-bugs
On Mon, Oct 21, 2013 at 6:41 PM,  <t.katsumata1122@gmail.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

pgsql-bugs by date:

Previous
From: t.katsumata1122@gmail.com
Date:
Subject: BUG #8542: Materialized View with another column_name does not work?
Next
From: Tomonari Katsumata
Date:
Subject: Re: BUG #8542: Materialized View with another column_name does not work?