Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tl9UZ-009hUS-UE for pgsql-general@arkaria.postgresql.org; Thu, 20 Feb 2025 16:33:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tl9UX-009c9s-V2 for pgsql-general@arkaria.postgresql.org; Thu, 20 Feb 2025 16:33:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tl9RL-009W7L-MC for pgsql-general@lists.postgresql.org; Thu, 20 Feb 2025 16:30:19 +0000 Received: from mail-ot1-x336.google.com ([2607:f8b0:4864:20::336]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tl9RJ-001vam-2m for pgsql-general@lists.postgresql.org; Thu, 20 Feb 2025 16:30:18 +0000 Received: by mail-ot1-x336.google.com with SMTP id 46e09a7af769-7271239d89fso299777a34.0 for ; Thu, 20 Feb 2025 08:30:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740069017; x=1740673817; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4g8o4vATirEX1sdP1baJsVS96upzCI8M588G7BPzCpE=; b=dKM80zwpkZTXKOKXvrsfyiJ/A5LmEUsKBrRVErA5cDaBipIAO5QyUotvjwXrfRh+qK +4WNYLHXuVbzNoDHBTv8/Y0oLYxAQDWATRiClqae/KLY5AX4eRIhiopU4v8vztMYSbwZ WTvOyHerPuk6pEXsIpQDmyVswN/HUBMCoiqU5Jf4Ee9xVsVHmDM8zg5oQF2uP46runma 9ukDWm4tvY84+B17RJ5D+6rAgbDxRYj/E6QdYauWW2qVuY0aJAeduucCoK+vVflDkD0s 1lF0uCS1MvHsiHxvjwCrGro117xVhaJeUm/aaT1DOXWSVZui7h65bAOlipEOB2f4UN4P tuyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740069017; x=1740673817; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=4g8o4vATirEX1sdP1baJsVS96upzCI8M588G7BPzCpE=; b=cr/3N9QaxXORxALxcmg1I5TGneIc7RRF3r0YrmSXLGtFSNQMxQF26tiDo9GEe2HcYY eS33fqFgdXMJsVHyey0+3SsPsTpcZxWzMrHAW3p5OFVGfhd3HXm/7hXFi6j1R8D81BSH GzEwEBaRsJsb9Hr2CE/JB1fgvGSI3owheac4uMLIjoUuuK+bg4zGkgnNMdnh2VdFlpTl CqOyasDJrmBdiJbxK4bIQFMgh1NBDAIphkilLAABi4yScp0LxnINbFlajB1XT0a2GRkC m1QbQLalCJGBT2F30C1t+h/DowwSnXTpj7kNByitAjRNhMjo2dEhw1L3B/6k4cVa3O3N J1aA== X-Forwarded-Encrypted: i=1; AJvYcCXd11qZOiPC5m5a2O4iZxiFxJqn88QgRkWsyLKLY1KUMC3g7Q6dHClA9C4PLW5jPXIGb9fhlWCJk6ooEP5p@lists.postgresql.org X-Gm-Message-State: AOJu0YxAvLqosMmfTAp04r7hYzu8XHgxvZ9buwz+jpJi1+AmCsdOsglR gl7hvJZG85F8f7nQPJuR8qNzsnJ0bxnhX2K+Aq8nBeAjvh9oHyUdqCiK4eRXG+SJ7Xza/NgNjkj Lji22Ac2Lob9Hzmh9ByMHB509D/g= X-Gm-Gg: ASbGncsEDYsMnRWAm347AA+H/1gyQPTctI8d9nG17ycCMwHjROWGzC1d9C3/K6XyW1a SUx1zo/OYvkbnnx0jmkpqFBYLZi3+JpuFUrl2TAU8o66zETxi99tSjx+crl3sQFrAPZMjgaU= X-Google-Smtp-Source: AGHT+IHnm6dy+igk2thJhReNjtIQvrFxbUZK5mFboLPoMtB0eJZX04eD1212g1QJxLUaCQqp2XOQhT7OV38VGdYkrJ4= X-Received: by 2002:a05:6808:f0c:b0:3f4:1bc5:762f with SMTP id 5614622812f47-3f41bc577b3mr2469856b6e.22.1740069017100; Thu, 20 Feb 2025 08:30:17 -0800 (PST) MIME-Version: 1.0 References: <2705563.1740067550@sss.pgh.pa.us> In-Reply-To: From: "David G. Johnston" Date: Thu, 20 Feb 2025 09:29:40 -0700 X-Gm-Features: AWEUYZlU1VRSrYxKNKQE3r2iGfUXuyjWJpghVvCP9khQMABv2qPgpzbXTCI93eE Message-ID: Subject: Re: DROP ROLE as SUPERUSER To: Dominique Devienne Cc: Tom Lane , "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000a62a4c062e95637b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a62a4c062e95637b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Feb 20, 2025 at 9:21=E2=80=AFAM Dominique Devienne wrote: > But that's not much better. It's basically like the SET ROLE to the > GRANTOR I did. > I guess what I want is GRANTED BY ANYONE! And not have to figure out > GRANTOR(s). > Your stated use case is dropping a role. Does the combination of reassign and drop owned not fulfill the requirements? https://www.postgresql.org/docs/current/role-removal.html Also, you had to know the role you wanted to drop so you already figured out the grantor. David J. --000000000000a62a4c062e95637b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Feb 20, 2025 at 9:21=E2=80=AFAM Dominique Devienne= <ddevienne@gmail.com> wro= te:
But that's not much better. It's basically like the SET ROLE t= o the GRANTOR I did.
I guess what I wa= nt is GRANTED BY ANYONE! And not have to figure out GRANTOR(s).
=

Your stated use case is dropping a rol= e.=C2=A0 Does the combination of reassign and drop owned not fulfill the re= quirements?


Also, you had to know the role you want= ed to drop so you already figured out the grantor.

Dav= id J.


--000000000000a62a4c062e95637b--