Re: patch: Add columns via CREATE OR REPLACE VIEW - Mailing list pgsql-hackers

From Robert Haas
Subject Re: patch: Add columns via CREATE OR REPLACE VIEW
Date
Msg-id 603c8f070811280548n52954dffpaee5f8f8d199e82b@mail.gmail.com
Whole thread Raw
In response to Re: patch: Add columns via CREATE OR REPLACE VIEW  (Bernd Helmle <mailings@oopsware.de>)
List pgsql-hackers
> I had a deeper look at this now. The patch looks clean and applies without
> any problems, regression tests passes. However, ATRewriteTables() has a
> problem when adding columns with domains and constraints. Consider this
> small test case:
>
> CREATE TABLE bar (id INTEGER);
> CREATE OR REPLACE VIEW vbar AS SELECT * FROM bar;
> CREATE DOMAIN person AS TEXT CHECK(value IN ('haas', 'helmle'));
> ALTER TABLE bar ADD COLUMN name person;
> CREATE OR REPLACE VIEW vbar AS SELECT * FROM bar;
>
> The last command confuses ATRewriteTable(), which wants to scan the relation
> leading to this error:
> ERROR:  could not open relation base/16384/16476:
>
> I see that ATRewriteTable() errors out on heap_beginscan(), since needscan
> is set to TRUE. One solution would be to teach ATRewriteTable(s) to handle
> view alteration differently in this case.

Thanks for the review - I'll take a look.

...Robert


pgsql-hackers by date:

Previous
From: "Robert Haas"
Date:
Subject: Re: PLUGINS Functionlity in Win32 build scripts
Next
From: Magnus Hagander
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new