Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iV0JH-0007U4-6r for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Nov 2019 21:36:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iV0JF-0005su-Km for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Nov 2019 21:36:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iV0JF-0005pb-60 for pgsql-hackers@lists.postgresql.org; Wed, 13 Nov 2019 21:36:17 +0000 Received: from mail-wm1-x336.google.com ([2a00:1450:4864:20::336]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iV0JC-0002PN-6K for pgsql-hackers@postgresql.org; Wed, 13 Nov 2019 21:36:16 +0000 Received: by mail-wm1-x336.google.com with SMTP id b17so3665865wmj.2 for ; Wed, 13 Nov 2019 13:36:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:user-agent:mime-version :content-transfer-encoding; bh=3Z+0IkfjVHypOUhYRRkLaafnOId/r54o1M4tZx0jqrE=; b=w/xfClLoW5oB1YCyN0Z00JwrxzF+Qg/x2GbYFKYrpleXLGwywXO9M84H/bfhX7ROpi uxaLk16VMQ3zH/gUYfiyNoOR3zo0gECJQahccpP8brJhoKQcKnecb75V3y66oomCxFKz w2wBEehaeHEZrPDosL+KBaLYr/VK8cHSMSLowc+uo/T5GKI2Fym7DEa3dUl2GtYCqgHl dqjHGRNR8J71CUth8nVH8YN1A5TsmmnyVFKPokUfRCK48Pz99UXHSC5/r5r5QUcaGfFG LJIeiKeGnjdDXCoM/RFW6B8yr4JVkv5bWX2T/Y9Qu+CLYzk3c9uhZ2Dke6WckBAbJ7BD dShQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:user-agent :mime-version:content-transfer-encoding; bh=3Z+0IkfjVHypOUhYRRkLaafnOId/r54o1M4tZx0jqrE=; b=FCVCq3JQCK8Wjq8r39CQoWmBL0U0GQOMTpDIOog11IbAHBsO0vRA5wJFSjvnCiDWTl GGTvG9HZOoXoN7wQh+/1EJeDYkvv6DBFrX2DWPpqK0Dfwph/AxPzumffJzTR9GZVCRsk wCDM6e7LQX0egroRseA7iPqiTHQOmt9j9HijtG2Y3mdYlnyw7O1hqdroALP+pQCwypBW XDMthVElXotGL5tnEwSrXt7LWtLdek1OrClAhpy/uJ6Ko9flOqqHaJSN214d5raXYDTn 8G7xi4hBWJBUWnsfXCPcSyhIVMq9KIB3YmwUv2ZTZHQa+GizkJQ7b/Y7tVX8r0guXPIk 9q7Q== X-Gm-Message-State: APjAAAXGaFW5qO1tMaLILTqLENAHI1J2UMPuyaIRSawLIvlC5m1bOkUw 9KsXaY14J8KW0sXJFAVbagM/MY0mvXFFtA== X-Google-Smtp-Source: APXvYqxuhT+fhVoQfFNoCbYzaxYNKwiaDvHdrOiuACt2QIVmSW6queasQb3d5lu3hMfDeE1HxCMI2w== X-Received: by 2002:a7b:c408:: with SMTP id k8mr5008543wmi.67.1573680972576; Wed, 13 Nov 2019 13:36:12 -0800 (PST) Received: from localhost.localdomain (217-149-175-116.nat.highway.telekom.at. [217.149.175.116]) by smtp.gmail.com with ESMTPSA id t5sm4222275wro.76.2019.11.13.13.36.11 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 13 Nov 2019 13:36:12 -0800 (PST) Message-ID: <504497aca66bf34bdcdd90bd0bcebdc3a33f577b.camel@cybertec.at> Subject: Role membership and DROP From: Laurenz Albe To: pgsql-hackers@postgresql.org Date: Wed, 13 Nov 2019 22:36:11 +0100 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.4 (3.32.4-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I realized only today that if role A is a member of role B, A can ALTER and DROP objects owned by B. I don't have a problem with that, but the documentation seems to suggest otherwise. For example, for DROP TABLE: Only the table owner, the schema owner, and superuser can drop a table. Should I compose a doc patch, or is that too much of a corner case to mention? I wanted to ask before I do the repetetive work. Yours, Laurenz Albe