Hi!
We've discussed the issue and got to conclusion - Postgres needs to
implement more granulated rights. Currently user after connecting to DB can
do almost anything, at least she can create its own tables and do whatever
she wants.
I want to compare the situation to MySQL. In this field MySQL design is
better than ours - in MySQL database admin can grant and revoke a lot of
rights for given DB - who can connect and from which host, who can CREATE
TABLEs, INSERT, UPDATE, DELETE, DROP and all that...
Oleg.
---- Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net Programmers don't die, they
justGOSUB without RETURN.
---------- Forwarded message ----------
Date: Sun, 1 Aug 1999 19:23:20 +0400 (MSD)
From: Dmitry Morozovsky <marck@rinet.ru>
To: pgsql-general@postgreSQL.org
Subject: [GENERAL] read-only databases
Hello there again.
Is there a way to make database 'db' for user 'john' read-only? I mean, is
there a way to disable 'create table/index/etc' SQL statements? I can make
read-only restrictions on existing tables, but -- what about creating new?
PgSQL 6.5, surely. Thanx in advance.
Sincerely,
D.Marck [DM5020, DM268-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------
