Tom Lane 7bae5a289c Get rid of the separate RULE privilege for tables: now only a table's owner ... can create or modify rules for the table. Do setRuleCheckAsUser() while loading rules into the relcache, rather than when defining a rule. This ensures that permission checks for tables referenced in a rule are done with respect to the current owner of the rule's table, whereas formerly ALTER TABLE OWNER would fail to update the permission checking for associated rules. Removal of separate RULE privilege is needed to prevent various scenarios in which a grantee of RULE privilege could effectively have any privilege of the table owner. For backwards compatibility, GRANT/REVOKE RULE is still accepted, but it doesn't do anything. Per discussion here: http://archives.postgresql.org/pgsql-hackers/2006-04/msg01138.php		2006-09-05 21:08:36 +00:00
..
Makefile	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00
rewriteDefine.c	Get rid of the separate RULE privilege for tables: now only a table's owner	2006-09-05 21:08:36 +00:00
rewriteHandler.c	Apply a simple solution to the problem of making INSERT/UPDATE/DELETE	2006-09-02 17:06:52 +00:00
rewriteManip.c	Remove 576 references of include files that were not needed.	2006-07-14 14:52:27 +00:00
rewriteRemove.c	Get rid of the separate RULE privilege for tables: now only a table's owner	2006-09-05 21:08:36 +00:00
rewriteSupport.c	Update copyright for 2006. Update scripts.	2006-03-05 15:59:11 +00:00