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

Problem with recent permission changes commits

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Problem with recent permission changes commits
Date: 2007-08-27 15:08:34
Message-ID: 46D2E8F2.9090802@commandprompt.com (view raw or flat)
Thread:
Lists: pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I just saw this in the weekly news:

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.

This is a problem. Our analytics software purposefully does not use a
super user, you are going to force the use of superusers with admin and
monitoring tools.

Of course this may be m00t if I am able to modify the GRANT?

Sincerely,

Joshua D. Drake


- --

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564   24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997  http://www.commandprompt.com/
			UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG0ujyATb/zqfZUUQRAhZSAJ4rhSGd6Cm/d6WU8JnZfXZ81axXtgCeKAfd
soW+ppLFZK/5UcBuQqrlNlM=
=u1jX
-----END PGP SIGNATURE-----

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-08-27 15:16:55
Subject: Re: Undetected corruption of table files
Previous:From: Andrew DunstanDate: 2007-08-27 15:00:12
Subject: MSVC build system

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