Ok, thanks for the explanation.
The SELECT FOR SHARE future solution sounds neat; I've solved the
actual problem in my application with a workaround.
-- Toni
>> CREATE DATABASE test_db;
>> CREATE USER test_user;
>> \c test_db test_user
>> CREATE TABLE test (id integer primary key);
>> CREATE TA
"toni garcia" writes:
> CREATE DATABASE test_db;
> CREATE USER test_user;
> \c test_db test_user
> CREATE TABLE test (id integer primary key);
> CREATE TABLE test_fk (id integer primary key, testid integer, constraint fk1
> foreign key (testid) references test(id));
> REVOKE UPDATE ON test FROM
The following bug has been logged online:
Bug reference: 4792
Logged by: toni garcia
Email address: agar...@at4.net
PostgreSQL version: 8.2.7
Operating system: gentoo linux
Description:odd behavior revoking perms on an owned table
Details:
Sorry, I cannot test on 8.
