[HACKERS] why restrict role public but not Public?

Hi, 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? -- Álvaro Herrera alvhe...@alvh.no-ip.org -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes

Re: [HACKERS] why restrict role public but not Public?

Alvaro Herrera alvhe...@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 that GRANT whatever TO

Re: [HACKERS] why restrict role public but not Public?

Excerpts from Tom Lane's message of mar ago 24 19:04:14 -0400 2010: Alvaro Herrera alvhe...@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

Re: [HACKERS] why restrict role public but not Public?

Alvaro Herrera alvhe...@commandprompt.com writes: The reason I'm asking is that I'm trying to allow public to be passed to has_table_privileges(), and have it check for the PUBLIC pseudo-role. Originally I had coded it using pg_strcasecmp() on the grounds that any case should refer to this.