CREATE MATERIALIZED VIEW statement ends up being CREATE TABLE AS statement underneath with table type matview. In that case, why don't I see special treatment only for materialized view and not CTAS in general, which allows column names to specified like the case in the bug reported.
On Fri, Nov 1, 2013 at 3:52 AM, Kevin Grittner <kgri...@ymail.com> wrote: > "t.katsumata1...@gmail.com" <t.katsumata1...@gmail.com> wrote: > > > I'm testing the Materialized View. > > When I've tried to create materialized view with specified > > column_name, I got an ERROR. > > > > example: > > - Creating original table > > CREATE TABLE t ( i int ); > > > > - 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" > > ---- > > > > I did not get any ERROR with non materialized view. > > CREATE VIEW mv_t(ii) AS SELECT * FROM t; > > > > Is this a bug or restriction for Materialized View? > > It's a bug. Will fix in the next 9.3 minor release. > > Moving the discussion to the -hackers list to discuss the fix. > > This bug was introduced in fb60e7296c2cf15195802b4596496b179bdc905a > based on this feedback: > > http://www.postgresql.org/message-id/20600.1363022...@sss.pgh.pa.us > > I picked the wrong response to that feedback. Attached is a patch > which fixes things along the alternative lines suggested. This > includes a regression test to ensure that this doesn't get broken > again. > > If there are no objections I'll apply this within a few days. > > -- > Kevin Grittner > EDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > > -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
