Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ovud0-0003Ne-8Z for pgsql-general@arkaria.postgresql.org; Fri, 18 Nov 2022 06:13:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ovucz-0007SL-39 for pgsql-general@arkaria.postgresql.org; Fri, 18 Nov 2022 06:13:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ovucy-0007SC-NZ for pgsql-general@lists.postgresql.org; Fri, 18 Nov 2022 06:13:28 +0000 Received: from mail-qt1-x82c.google.com ([2607:f8b0:4864:20::82c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ovucw-0006ne-9F for pgsql-general@lists.postgresql.org; Fri, 18 Nov 2022 06:13:27 +0000 Received: by mail-qt1-x82c.google.com with SMTP id cg5so2559169qtb.12 for ; Thu, 17 Nov 2022 22:13:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=a9xxlV39bt1eHasn95vSr1lLNZYTpA8om6IVcApfM28=; b=PHFQkCGvy52K3VK5AQyFFrYn5ggHCsPJJH0pRxx6HeuJ4gqegjHFpBZhMUZZe32G+P S3kja0lstVv5enTGEdBn0Q/MPcl2HxVyXUfAnIxWWhCt/niO5R5VYQPAFbZPR16HnBLd SWdACtD7JUQ/9TeoQGDtCxKZ15nYetDNaG7cXmFatlVrQXHyJOz43A1fn0m858ga3Mma S5nX6FznX5oA7GqKlc02BFXL3bcjrSBvRBka5hDXrZh4bMZTFU00WtGEaKKmZzJSRvfa sbetEGMiXzUx4jlZ8Eh7vgpYpJiH06hbJTAYbg2oCejIeDQx9orPo8F+gM2pdO2Dxs78 4JrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=a9xxlV39bt1eHasn95vSr1lLNZYTpA8om6IVcApfM28=; b=sdSijRp/CbJnyZCvBXZU/SZXIm+VSGqMK0Q+TnXcDVvbc4iRN7pUKNGVNK8Akv2TG3 pPrcnjPtMzwl3ZWO5eS3/FFgBog2IL8Exk1P2dcoC1w25DKYM5hTHqyxrcOAB9Xj+CX7 zYTly7dWVfMAZ/3wKNM+jB52rGAu4dQ8O/nB0Fe3LVAKeyhmu3qllLImG+rYCVruMreC w9/s/IJFmo4eaqHQy1zreo7+g9j5mfXdVmoOjEmUYYwQArYgQ/htmEq82gBeoHpsOinR kVq8A/hoPMd7EeiE8V3WVJlGme1EmmDDTemlJ1Ocd3nfcEn9CNX523MQw3yFlgk3v8co b0KQ== X-Gm-Message-State: ANoB5plMEN3QdIRxFsJ+axtBj5+OQ9Ri+c2uNd05SfzvraOmczAZQVyu SJ3Z8wJNywwr/6+9MOP38aSAtUiBOtk= X-Google-Smtp-Source: AA0mqf6ELcBVBDXPZrLrNpM0MqmnNGgxBUlCI4T/p+n70c0kRdo1Qb7ZGBkVAJFrE4B/NNiArzBYLw== X-Received: by 2002:a05:622a:1e8c:b0:3a5:62:af4f with SMTP id bz12-20020a05622a1e8c00b003a50062af4fmr5270802qtb.431.1668752004999; Thu, 17 Nov 2022 22:13:24 -0800 (PST) Received: from ?IPV6:2600:1700:bd2c:b810::43? ([2600:1700:bd2c:b810::43]) by smtp.googlemail.com with ESMTPSA id bk23-20020a05620a1a1700b006ce580c2663sm1872370qkb.35.2022.11.17.22.13.24 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 17 Nov 2022 22:13:24 -0800 (PST) Message-ID: Date: Fri, 18 Nov 2022 00:13:24 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: Drop role cascade ? Content-Language: en-US To: pgsql-general@lists.postgresql.org References: From: Ron In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/17/22 17:07, David Gauthier wrote: > psql (11.5, server 11.3) on linux > > Someone who had privileges in a lot of tables/schemas/DBs left the > company.  I want to drop that role but "rop role xxx" won't let me > because...  "xxx cannot be dropped because some objects depend on it". > > Is there a way to just get rid of this role without revoking xxx in all > the individual DB objects he has privs too?  Something like "drop role xxx > cascade" ? Had this idea tonight about how to find what is owned by a specific role.  Haven't tested it, so the syntax might be a bit wrong, and it might not work: $ pg_dump --schema-only $DATABASE | grep OWNER | grep $OLDEMPLOYEE -- Angular momentum makes the world go 'round.