Skip site navigation (1) Skip section navigation (2)

pgsql/src/backend/tcop (utility.c)

From: Bruce Momjian - CVS <momjian>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql/src/backend/tcop (utility.c)
Date: 2000-09-12 04:49:12
Message-ID: 200009120449.e8C4nCd10415@hub.org (view raw or flat)
Thread:
Lists: pgsql-committers
  Date: Tuesday, September 12, 2000 @ 00:49:11
Author: momjian

Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/tcop
     from hub.org:/home/projects/pgsql/tmp/cvs-serv10314/pgsql/src/backend/tcop

Modified Files:
	utility.c 

-----------------------------  Log Message  -----------------------------

This patch implements a different "relkind"
for views. Views are now have a "relkind" of
RELKIND_VIEW instead of RELKIND_RELATION.

Also, views no longer have actual heap storage
files.

The following changes were made

1. CREATE VIEW sets the new relkind

2. The executor complains if a DELETE or
        INSERT references a view.

3. DROP RULE complains if an attempt is made
        to delete a view SELECT rule.

4. CREATE RULE "_RETmytable" AS ON SELECT TO mytable DO INSTEAD ...
        1. checks to make sure mytable is empty.
        2. sets the relkind to RELKIND_VIEW.
        3. deletes the heap storage files.
5. LOCK myview is not allowed. :)


6. the regression test type_sanity was changed to
        account for the new relkind value.

7. CREATE INDEX ON myview ... is not allowed.

8. VACUUM myview is not allowed.
        VACUUM automatically skips views when do the entire
        database.

9. TRUNCATE myview is not allowed.


THINGS LEFT TO THINK ABOUT

o pg_views

o pg_dump

o pgsql (\d \dv)
o Do we really want to be able to inherit from views?

o Is 'DROP TABLE myview' OK?

-- 
Mark Hollomon


pgsql-committers by date

Next:From: Bruce Momjian - CVSDate: 2000-09-12 04:49:15
Subject: pgsql/src/backend/utils/cache (relcache.c)
Previous:From: Bruce Momjian - CVSDate: 2000-09-12 04:49:11
Subject: pgsql/src/backend/rewrite (rewriteDefine.c rewriteRemove.c)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group