Tom Lane wrote:
> Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> writes:
>> OK, I'll add the following description in the documentation of pg_largeobject.
>> <structname>pg_largeobject</structname> should not be readable by the
>> public, since the catalog contains data in large objects of all users.
> This is going to be a problem, because it will break applications that
> expect to be able to read pg_largeobject. Like, say, pg_dump.
Is it a right behavior, even if we have permission checks on large objects?
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.
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
In response to
pgsql-hackers by date
|Next:||From: Jaime Casanova||Date: 2009-12-11 05:10:29|
|Subject: Re: Largeobject Access Controls (r2460)|
|Previous:||From: Robert Haas||Date: 2009-12-11 04:55:49|
|Subject: Re: [PATCH] dtrace probes for memory manager|