Horton

Re: BUG #14242: Role with a setconfig "role" setting to a nonexistent role causes pg_upgrade to fail

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Gierth <andrew@tao11.riddles.org.uk>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, "bossartn\@amazon.com" <bossartn@amazon.com>, "pgsql-bugs\@postgresql.org" <pgsql-bugs@postgresql.org>
Date: 2016-07-11T23:22:12Z
Lists: pgsql-bugs 
Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
> I don't think this is documented but it has obvious uses.

Does it?  If the named role is the same as the actual role, then it's
useless.  If they're different, it seems at best confusing.  In the
context of ALTER DATABASE SET, it seems both confusing and possibly
a security hazard.

			regards, tom lane

Commits

  1. Fix some inappropriately-disallowed uses of ALTER ROLE/DATABASE SET.