pgsql: Don't handle PUBLIC/NONE separately

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't handle PUBLIC/NONE separately
Date: 2015-07-20 16:47:49
Message-ID: E1ZHEEH-0002J2-O4@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Don't handle PUBLIC/NONE separately

Since those role specifiers are checked in the grammar, there's no need
for the old checks to remain in place after 31eae6028ec. Remove them.

Backpatch to 9.5.

Noted and patch by Jeevan Chalke

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/e52b690cf55f303839f12f8f1f136d2366d36298

Modified Files
--------------
src/backend/commands/user.c | 14 --------------
1 file changed, 14 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2015-07-20 19:46:35 pgsql: Sanity-check that a page zeroed by redo routine is marked with W
Previous Message Teodor Sigaev 2015-07-20 15:19:22 pgsql: This supports the triconsistent function for pg_trgm GIN opclass