Re: [PATCH] Largeobject access controls

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
Cc: KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Largeobject access controls
Date: 2009-09-24 06:00:56
Message-ID: 3073cc9b0909232300x7db74456lf4ce5e9abc91e590@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2009/9/24 KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)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...

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message KaiGai Kohei 2009-09-24 06:16:46 Re: [PATCH] Largeobject access controls
Previous Message Jaime Casanova 2009-09-24 05:56:28 Re: [PATCH] Largeobject access controls