From: Bossart, Nathan <bossartn@amazon.com>
To: Andrew Gierth <andrew@tao11.riddles.org.uk>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
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 23:22:02 +0000
Message-ID: <b7d103be7cbc4714963e6326c802b023@EX13D03UWC002.ant.amazon.com> (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>
I cannot speak to any real use-cases beyond easily altering current_user every time you start a session.
Besides disallowing this parameter in ALTER ROLE SET statements entirely, perhaps pg_dumpall could simply skip it for missing roles? I cannot think of a use-case for maintaining an invalid setting here.
Nathan
--
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: bossartn@amazon.com, andrew@tao11.riddles.org.uk, david.g.johnston@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: BUG #14242: Role with a setconfig "role" setting to a nonexistent role causes pg_upgrade to fail
In-Reply-To: <b7d103be7cbc4714963e6326c802b023@EX13D03UWC002.ant.amazon.com>
* 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