On Fri, 26 Jan 2001, [koi8-r] íÁËÓÉÍ í. đĎĚŃËĎ× wrote:
> Good Day, Dear Karel Zak!
>
> Please, forgive me for my bad english and if i do not right with your
> day time.
my English is more poor :-)
You are right, it is (was?) in TODO and it will implemented - I hope -
in some next release (may be in 7.2 during ACL overhaul, Peter?).
Before some time I wrote patch that resolve it for 7.0.2 (anyone -
I forgot his name..) port it to 7.0.2, my original patch was for 7.0.0.
May be will possible use it for last stable 7.0.3 too.
The patch is at: ftp://ftp2.zf.jcu.cz/users/zakkr/pg/7.0.2-user.patch.gz
This patch add to 7.0.2 code NOCREATETABLE and NOLOCKTABLE feature:
CREATE USER username [ WITH [ SYSID uid ] [ PASSWORD 'password' ] ] [ CREATEDB | NOCREATEDB ] [ CREATEUSER
|NOCREATEUSER ]
-> [ CREATETABLE | NOCREATETABLE ] [ LOCKTABLE | NOLOCKTABLE ] ...etc.
If CREATETABLE or LOCKTABLE is not specific in CREATE USER command,
as default is set CREATETABLE or LOCKTABLE (true).
But, don't forget - it's temporarily solution, I hope that some next
release resolve it more systematic. More is in the patche@postgresql.org
archive where was send original patch.
Because you are not first person that ask me, I re-post (CC:) it to
hackers@postgresql.org, more admins happy with this :-) Karel
> I want to ask You about "access control over who can create tables and
> use locks in PostgreSQL". This message was placed in PostgreSQL site
> TODO list. But now it was deleted. I so need help about this question,
> becouse i'll making a site witch will give hosting for our users.
> And i want to make a PostgreSQL access to their own databases. But there
> is (how You now) one problem. Anyone user may to connect to the different
> user database and he may to create himself tables.
> I don't like it.
