On Fri, 2005-09-30 at 09:14, jeff sacksteder wrote:
> Are there any data access issues (as opposed to data visibility
> issues)
> you are having?
>
>
> No, It's just that in a hosting situation where each customer has a
> database of their own, they need to be boxed in somehow. In
Are there any data access issues (as opposed to data visibility issues)
you are having?
No, It's just that in a hosting situation where each customer has a
database of their own, they need to be boxed in somehow. In the event
of an application bug allowing raw sql to be executed, it's not
appropri
jeff sacksteder wrote:
The security documentation available in the official documentation is rather
sparse. Is there a more detailed document I should be aware of?
No.
As an example, I'd like to prevent a a user from being able to get a list of
existing databases. Presumably, I can limit acce
Am Donnerstag, 29. September 2005 21:46 schrieb jeff sacksteder:
> As an example, I'd like to prevent a a user from being able to get a list
> of existing databases.
You can't do that.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)
The security documentation available in the official documentation is
rather sparse. Is there a more detailed document I should be aware of?
As an example, I'd like to prevent a a user from being able to get a
list of existing databases. Presumably, I can limit access to various
system catalogs to
