Egg in the face time.  I knew it was going to be one of those...


CREATE ROLE  --DOES NOT EQUAL--  CREATE USER

Whereas the latter implies LOGIN priv, the former does not.
I'd read about LOGIN auto-implied some time ago, but I'd not noticed that is not so w/ a created ROLE.


Maybe you can smell the sulfur from where you are?


Ralph Smith

=====================



On Apr 4, 2008, at 2:57 PM, Tom Lane wrote:
Ralph Smith <[EMAIL PROTECTED]> writes:
However I'm now trying to access it using all lower case.
Are you saying that IT'S confused and I should go all lower or use
quotes (") not (')?

Well, you can do it either way.

If you want the database to be really truly named "LabNews_dev"
(mixed case) then you need to create it using the quotes, and then
you'll have to use quotes *every* time you name it in SQL commands,
and you'll have to be careful to use the mixed-case spelling in
other contexts such as pg_hba.conf and psql command arguments.

If you are okay with it really being named "labnews_dev" then you
won't need quotes in your SQL commands, but you'll have to spell
it in all lower case in pg_hba.conf and psql command arguments.

                        regards, tom lane


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Reply via email to