Arturs Zoldners <az(at)rpiva(dot)lv> writes:
> -- The following rule prevents user x to update public_data:
> CREATE RULE log_public AS ON UPDATE TO private_data WHERE (new.a <>
> old.a) DO INSERT INTO private_log (old_val, new_val) VALUES (old.a,
This is a known problem. It's fixed for 7.5 but there seems no way to
back-port the fix into existing release series (without forcing initdb).
The error is essentially that the use of an INSERT command as the rule
body causes the original view to be checked for INSERT rather than
UPDATE permissions ...
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2004-04-30 16:52:05|
|Subject: Re: [BUGS] BUG #1134: ALTER USER ... RENAME breaks md5 passwords |
|Previous:||From: PostgreSQL Bugs List||Date: 2004-04-30 15:43:17|
|Subject: BUG #1145: silent REVOKE failures|