From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Revoke - database does not exist |
Date: | 2014-05-02 01:20:05 |
Message-ID: | 1398993605624-5802185.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Prashanth Kumar wrote
> Hi,
>
> Do not seem to figure out what is wrong here. Why am I getting database
> does not exist. I just created the database and am able to connect to it
> as "postgres" user.
> I am trying to restrict "testuser" from connecting to "myDB" database.
Thomas is likely correct about the quoting. The command programs are
case-sensitive and perform the proper quoting for you when issuing commands;
but when you are inside psql you need to take care to perform the proper
quoting yourself.
WRT grant/revoke keep in mind when you revoke you only remove pre-existing
grants; it does not establish an explicit block on its own. i.e., it
doesn't stop default permissions, or those inherited from PUBLIC, from
applying. You would need to remove those inheritance-granted permissions
and then explicitly grant them back to those who still require them while
omitting those that do not.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Revoke-database-does-not-exist-tp5802183p5802185.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Tim van der Linden | 2014-05-02 07:54:57 | Full text: Ispell dictionary |
Previous Message | Tomáš Vondra | 2014-05-02 01:02:08 | Re: Revoke - database does not exist |