Re: permission denied for tablespace pg_global?

From: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: permission denied for tablespace pg_global?
Date: 2007-10-10 16:49:30
Message-ID: 014b01c80b5d$87abdab0$0c01a8c0@yourc3ftrhkaod
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Sent: Wednesday, October 10, 2007 9:55 PM
Subject: Re: [HACKERS] permission denied for tablespace pg_global?

> "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp> writes:
>> postgres=# SELECT pg_size_pretty(pg_tablespace_size(1664));
>> ERROR: permission denied for tablespace pg_global
>
> This is an intentional change, documented in the release notes:
>
> * Put some security restrictions on the dbsize functions (Tom)
>
> Restrict pg_database_size() to users who can connect to the target
> database (note that CONNECT privilege is granted by default, so this
> does not change the default behavior). Restrict pg_tablespace_size()
> to users who have CREATE privilege on the tablespace (which is not
> granted by default), except when the tablespace is the default
> tablespace for the current database (since we treat that as implicitly
> allowing use of the tablespace).
>
> There was a long thread about this in -hackers two months ago:
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00948.php
>
> regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Glaesemann 2007-10-10 16:51:28 Re: quote_literal with NULL
Previous Message Tom Lane 2007-10-10 16:43:17 Re: Timezone database changes