-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua D. Drake wrote:
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
On Mon, Aug 27, 2007 at 08:08:34AM -0700, Joshua D. Drake wrote:
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Decibel! wrote:
On Mon, Aug 27, 2007 at 08:08:34AM -0700, Joshua D. Drake wrote:
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.
On Mon, Aug 27, 2007 at 11:59:05AM -0700, Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Decibel! wrote:
On Mon, Aug 27, 2007 at 08:08:34AM -0700, Joshua D. Drake wrote:
This is a problem. Our analytics software purposefully does not use a
super user, you are
