Re: BUG #8542: Materialized View with another column_name does not work?
От | Tomonari Katsumata |
---|---|
Тема | Re: BUG #8542: Materialized View with another column_name does not work? |
Дата | |
Msg-id | CAC55fYe5Pf=TNr8fuAdtwMXK++jSDXm-kjrivtvVX28p3XWkhA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #8542: Materialized View with another column_name does not work? (Michael Paquier <michael.paquier@gmail.com>) |
Список | pgsql-bugs |
Hi Michael, Thank you for replying! I understand it seems a bug. After some trying, I got a workaround for this. CREATE MATERIALIZED VIEW mv_t AS SELECT i ii FROM t; This seems working fine. 2013/10/21 Michael Paquier <michael.paquier@gmail.com> > 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 по дате отправления: