Re: why restrict role "public" but not "Public"?

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