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>
Cc: bossartn\@amazon.com <bossartn@amazon.com>
Cc: pgsql-bugs\@postgresql.org <pgsql-bugs@postgresql.org>
Subject: Re: BUG #14242: Role with a setconfig "role" setting to a nonexistent role causes pg_upgrade to fail
Date: Mon, 11 Jul 2016 19:22:12 -0400
Message-ID: <15762.1468279332@sss.pgh.pa.us> (raw)
In-Reply-To: <87oa633gzm.fsf@news-spur.riddles.org.uk>
References: <20160711223641.1426.86096@wrigleys.postgresql.org>
<14434.1468277346@sss.pgh.pa.us>
<CAKFQuwakeJGHp+4qOZwGtMXV2B4ML69HRdcpx8F9XzKTc725qQ@mail.gmail.com>
<87oa633gzm.fsf@news-spur.riddles.org.uk>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew@tao11.riddles.org.uk, david.g.johnston@gmail.com, bossartn@amazon.com
Subject: Re: BUG #14242: Role with a setconfig "role" setting to a nonexistent role causes pg_upgrade to fail
In-Reply-To: <15762.1468279332@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox