Re: [ANNOUNCE] == PostgreSQL Weekly News - August 26 2007 == - Mailing list pgsql-general

From Joseph S
Subject Re: [ANNOUNCE] == PostgreSQL Weekly News - August 26 2007 ==
Date
Msg-id fav1vj$2ui3$1@news.hub.org
Whole thread Raw
In response to Re: [ANNOUNCE] == PostgreSQL Weekly News - August 26 2007 ==  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom Lane wrote:
> Joseph S <jks@selectacast.net> writes:
>>> Tom Lane committed:
>>> - Restrict pg_relation_size to relation owner, pg_database_size to DB
>>> owner, and pg_tablespace_size to superusers.  Perhaps we could
>>> weaken the first case to just require SELECT privilege, but that
>>> doesn't work for the other cases, so use ownership as the common
>>> concept.
>>>
>> Is there going to be a way to turn this off easily?
>
> No.  If you want to make an argument for weaker restrictions than these,
> argue away, but security restrictions that can be "easily turned off"
> are no security at all.

I don't see how letting the size of a database or relation is a big
security risk.  I do see how forcing me to login as the superuser to see
my db stats creates more of a security risk.

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: PostgreSQL vs Firebird feature comparison finished
Next
From: Kevin Neufeld
Date:
Subject: PickSplit method of 2 columns ... error