Jaime Casanova wrote: > 2009/9/24 KaiGai Kohei <kai...@ak.jp.nec.com>: >> Example) >> postgres=# SET SESSION AUTHORIZATION ymj; >> SET >> postgres=> SELECT loread(lo_open(16453, x'40000'::int), 20); >> ERROR: permission denied for largeobject 16453 >> >> postgres=# SET largeobject_compat_acl = on; <---- enables >> compatible mode >> SET (Only superuser >> can set it) >> postgres=# SET SESSION AUTHORIZATION ymj; >> SET >> postgres=> SELECT loread(lo_open(16453, x'40000'::int), 20); >> NOTICE: permission denied for largeobject 16453 <---- dose not >> prevent it > > i'm not really sure the warnings are worth the trouble but if you want > to do it then the NOTICE version should use another message... i'm not > comfortable with a "permission denied" that is simply ignored...
It is not a significant issue whether the compatible mode allows users to bypass ACL checks with or without any notifications. Which is the preferable one? 1. It always generates notifications whenever access violations. 2. It generates notifications at the first violation only. 3. It never generates notifications. Thanks, -- OSS Platform Development Division, NEC KaiGai Kohei <kai...@ak.jp.nec.com> -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
