Zdenek Kotala <[EMAIL PROTECTED]> writes:
> I still does not see any benefit from user side why postgres has this
> exception. It is confusing and it should generate potential security
> risk.
"Security risk"? Now you're just making things up.
regards, tom lane
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
It's presumed that the right to create tables within a database entails
the right to create them someplace; hence no permissions check is made
on the database's default tablespace. Without that, not only does plain
CREAT
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> It's presumed that the right to create tables within a database entails
>> the right to create them someplace; hence no permissions check is made
>> on the database's default tablespace. Without that, not only does plain
>> CREATE TABL
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
It seems that we not able to revoke create privilege on default tablespace.
This is intentional.
I don't understand why.
It's presumed that the right to create tables withi
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Zdenek Kotala <[EMAIL PROTECTED]> writes:
>>> It seems that we not able to revoke create privilege on default tablespace.
>>
>> This is intentional.
> I don't understand why.
It's presumed that the right to create tables within a dat
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
It seems that we not able to revoke create privilege on default tablespace.
This is intentional.
I don't understand why. I did not find any mention about this in the
documentation. Please, could you explain it?
Than
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> It seems that we not able to revoke create privilege on default tablespace.
This is intentional.
regards, tom lane
---(end of broadcast)---
TIP 5: don't forget to increase your fre
