public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Robert Haas <[email protected]>
Cc: Zach Manifold <[email protected]>
Cc: [email protected]
Subject: Re: Proposal: DROP ROLE ... REASSIGN OWNED TO ...
Date: Fri, 24 Apr 2026 21:12:56 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+Tgmoavbii-G1uN9tB=gDFJqwp2W-mVM80NifURWb+mDmFc3g@mail.gmail.com>
References: <CACLQnSmysDOQEn9HJ+AEXMxQ0KvNg=T3+Emz65jkVSqxXaNcPQ@mail.gmail.com>
<CA+Tgmoavbii-G1uN9tB=gDFJqwp2W-mVM80NifURWb+mDmFc3g@mail.gmail.com>
Robert Haas <[email protected]> writes:
> This would fail if the user to be dropped owned objects in another
> database, but your hypothetical version of DROP ROLE would have that
> issue, too. Even if you couldn't wrap both commands in a single
> transaction -- we have some DDL commands that are like that -- running
> them one after another wouldn't lose much. So I'm just not sure I
> really see the point.
Yeah. We intentionally separated this functionality because the
expectation is that you'll likely have to do REASSIGN OWNED in
multiple databases before DROP ROLE will succeed. So I'm not
much in favor of adding a combined command; it will just lead
people to try to do things that won't work.
regards, tom lane
view thread (4+ messages)
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Proposal: DROP ROLE ... REASSIGN OWNED TO ...
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox