Skip site navigation (1) Skip section navigation (2)

Re: Largeobject Access Controls (r2460)

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Largeobject Access Controls (r2460)
Date: 2009-12-11 05:10:29
Message-ID: 3073cc9b0912102110k581b6423i6b92ecc2a38b9d19@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2009/12/10 KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>:
>
> If so, we can inject a hardwired rule to prevent to select pg_largeobject
> when lo_compat_privileges is turned off, instead of REVOKE ALL FROM PUBLIC.
>

it doesn't seem like a good idea to make that GUC act like a GRANT or
REVOKE on the case of pg_largeobject.
besides if a normal user can read from pg_class why we deny pg_largeobject

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

In response to

Responses

pgsql-hackers by date

Next:From: Jaime CasanovaDate: 2009-12-11 05:11:11
Subject: Re: thread safety on clients
Previous:From: KaiGai KoheiDate: 2009-12-11 04:57:27
Subject: Re: Largeobject Access Controls (r2460)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group