Re: why restrict role "public" but not "Public"? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: why restrict role "public" but not "Public"?
Date
Msg-id 7096.1282691054@sss.pgh.pa.us
Whole thread Raw
In response to why restrict role "public" but not "Public"?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: why restrict role "public" but not "Public"?  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> I just noticed that we restrict creation of a role named "public", but
> this is case-sensitive -- i.e. we don't restrict roles named PUBLIC,
> etc.

> Is this intended?

Yes.  If you had a role named that, you might think thatGRANT whatever TO PUBLIC
should refer to that role.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: why restrict role "public" but not "Public"?
Next
From: Alvaro Herrera
Date:
Subject: Re: why restrict role "public" but not "Public"?