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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: [ANNOUNCE] == PostgreSQL Weekly News - August 26 2007 ==


  • From: Joseph S <jks(at)selectacast(dot)net>
  • To: pgsql-general(at)postgresql(dot)org
  • Subject: Re: [ANNOUNCE] == PostgreSQL Weekly News - August 26 2007 ==
  • Date: Mon, 27 Aug 2007 13:34:43 -0400
  • Message-id: <fav1vj$2ui3$1(at)news(dot)hub(dot)org>

Tom Lane wrote:
Joseph S <jks(at)selectacast(dot)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.



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group