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 1rbjBC-00GhVA-1p for pgsql-general@arkaria.postgresql.org; Sun, 18 Feb 2024 15:34:10 +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 1rbjB9-00AEdG-QV for pgsql-general@arkaria.postgresql.org; Sun, 18 Feb 2024 15:34:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rbjB9-00AEd6-BT for pgsql-general@lists.postgresql.org; Sun, 18 Feb 2024 15:34:07 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rbjB1-007qKJ-Sv for pgsql-general@lists.postgresql.org; Sun, 18 Feb 2024 15:34:06 +0000 Received: from [192.168.0.104] (unknown [62.217.189.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: p.luzanov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id C0401E20E20; Sun, 18 Feb 2024 18:33:57 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1708270437; bh=pUIcuHfaPgui6gVgXKOIOpZ3TrleWS3ZaYPYx5blO/o=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=uwTs6ge5mIp4yYFnfs10df+QSRUA3uvGgTgMS6Zlm/hnLuWZR2qPOYxzOkj+aEg3X MLt1qu4WvhgchbbIDCLvt6RTXJP2ni55wd7jVrSwY4Gb5tYht2cTuWvBxSyTgH4MFg DKK6kePJgN4VZMS8o3Eq/5z8mbR3US78D5G0qcO2YsnScr438FWlkxaE6se1jQaq6L KHNOh3nddFRrSr+MUEUEE9nclmTmh7nSDCq7+mDgbREoR1tsKvP6YsBVabPrxpZWBs 9tDfhnPc7O2QhQbXVQBoPMeFMVPu5/fryPwbilC1275G1/XG3ObwnuSDQmxHJB1KCV 4oHxhc3LOk7PA== Content-Type: multipart/alternative; boundary="------------h2dJuhUm0kDNBy2xpk1S0DOr" Message-ID: <4d9f0928-950c-401d-b2d3-f11faf39a1fb@postgrespro.ru> Date: Sun, 18 Feb 2024 18:33:57 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Users and object privileges maintenance Content-Language: en-US, ru-RU To: Dominique Devienne Cc: Laurenz Albe , Lok P , pgsql-general References: <459ef527-5d83-4bed-90d5-4bbabc1da91c@postgrespro.ru> From: Pavel Luzanov In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------h2dJuhUm0kDNBy2xpk1S0DOr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 18.02.2024 17:40, Dominique Devienne wrote: > Well, membership in a role mean you can "become that role", no? Thus > this seems logical, > and not confusing to me, that you can act as the owner, since you SET > ROLE to the owner. They may acts as the owner even without explicit SET ROLE to the owner. It wasn't obvious to me when I came to postgres from oracle. -- Pavel Luzanov Postgres Professional:https://postgrespro.com --------------h2dJuhUm0kDNBy2xpk1S0DOr Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit On 18.02.2024 17:40, Dominique Devienne wrote:
Well, membership in a role mean you can "become that role", no? Thus this seems logical,
and not confusing to me, that you can act as the owner, since you SET ROLE to the owner.
They may acts as the owner even without explicit SET ROLE to the owner.
It wasn't obvious to me when I came to postgres from oracle.
-- 
Pavel Luzanov
Postgres Professional: https://postgrespro.com
--------------h2dJuhUm0kDNBy2xpk1S0DOr--