Re: permission denied for tablespace pg_global? - Mailing list pgsql-hackers

From Hiroshi Saito
Subject Re: permission denied for tablespace pg_global?
Date
Msg-id 014b01c80b5d$87abdab0$0c01a8c0@yourc3ftrhkaod
Whole thread Raw
In response to permission denied for tablespace pg_global?  ("Hiroshi Saito" <z-saito@guitar.ocn.ne.jp>)
List pgsql-hackers
----- Original Message ----- 
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Hiroshi Saito" <z-saito@guitar.ocn.ne.jp>
Cc: <pgsql-hackers@postgresql.org>
Sent: Wednesday, October 10, 2007 9:55 PM
Subject: Re: [HACKERS] permission denied for tablespace pg_global? 


> "Hiroshi Saito" <z-saito@guitar.ocn.ne.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Timezone database changes
Next
From: Tom Lane
Date:
Subject: Re: quote_literal with NULL