Re: psql: FATAL: role "xyz" is not permitted to log in

From: Ralph Smith <smithrn(at)washington(dot)edu>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: psql: FATAL: role "xyz" is not permitted to log in
Date: 2008-04-04 22:54:54
Message-ID: 04F674C0-D9AE-4895-A09D-F455A61A310C@washington.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 <smithrn(at)washington(dot)edu> 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Markus Wollny 2008-04-04 22:57:42 Duplicate Key violation on dump&reload using pg_restore
Previous Message Gregory Stark 2008-04-04 22:20:10 Re: modules