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 1rf4Jt-00FFsd-Ay for pgsql-general@arkaria.postgresql.org; Tue, 27 Feb 2024 20:44:58 +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 1rf4Js-0062e8-0D for pgsql-general@arkaria.postgresql.org; Tue, 27 Feb 2024 20:44:56 +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 1rf4Jq-0062e0-8S for pgsql-general@lists.postgresql.org; Tue, 27 Feb 2024 20:44:56 +0000 Received: from wfout6-smtp.messagingengine.com ([64.147.123.149]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rf4Jh-001bF3-Nb for pgsql-general@lists.postgresql.org; Tue, 27 Feb 2024 20:44:53 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfout.west.internal (Postfix) with ESMTP id 2EBE41C00092; Tue, 27 Feb 2024 15:44:44 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Tue, 27 Feb 2024 15:44:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1709066683; x=1709153083; bh=knVSQeemvr94UekK2OrfHQuU+nVP+Yz6m8DlIpRIXLU=; b= iwHk/MdU3n031mksdhLMoTFu1H7u2p58t5VTGVNS9mTilYCLuqMFKv0g+6z+uCGD 9GA60MZtp7ktPSaLjfbmwZLufAfpIUq8NlseUCU4vZG5G7DUuSRej1Ef9/U/Tcn0 VdwIKfZrl2tzfLFaYq/N2UEahbez6VyqS5K3Dp7z2S8voGYyMnPfqsZtZTXx6Ei7 /O4zIV+ROjY1o8PGt+HYOCfoxr1UFSpX9ewvrwOXFkfLJALgLw4C/jUoBefnvF75 DvJnNOwBtLjFyi2Rcc5kyG/w4ose2HY8klYsxQkxaAE3uHtJ4/DYuwBfdvV/B5O6 SL8fB2ruWhUPDkNNwU1Mqw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1709066683; x= 1709153083; bh=knVSQeemvr94UekK2OrfHQuU+nVP+Yz6m8DlIpRIXLU=; b=P ZJ4Obmx4xJk56/QD3IPhdoMA9aze3jzVmVVSEMeLQHqkWnZ8Lxhm6E4/EY+4Dcjb U1n5JubSW1IwhWvWHM+JCYztvwpSxcA9oMFPvpz4RYxESJAWktIXa2HXG6yMVoxK 8jSdVw6/TLdPl1g1nMhZpDZhZ7Il9hA+7CSWJQaAaqNHKWSmBytSHHmmF/J8Q4Fw D0sjbaUUIgtWxKxYN3EXZTKc7MyDylvcDt6aIynK/nhqSc5IcEcpFjbI0OQ0/gjh CA4SXxagbSNBNEwFPTaqjJ1svgpTO+oTYqBNiV/XklEEnzFe2xKhfo3n65k7PMSG glURS01WSWpit9VLQJMng== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrgeehgdduudeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeelgeevkeekkeeuiefgtdevieeluefhfedufeetkeej ffekjeeujeehgeehgeektdenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhi rghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 27 Feb 2024 15:44:43 -0500 (EST) Message-ID: <481d67c0-aef6-415b-9643-75ffce926fcb@aklaver.com> Date: Tue, 27 Feb 2024 12:44:42 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Aligning grants and privileges Content-Language: en-US To: veem v , pgsql-general References: From: Adrian Klaver 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 2/27/24 12:40, veem v wrote: > Hi, > We have two different types of DBA group in current on-premise Oracle > databases,  one who deploy code in prod and highest level of privileges > (i.e having write access to the database objects, performing backup > recovery, export/import and performing other database maintenance jobs etc). > > and other groups, who only have read only privileges (select catalogue > role i.e access to data dictionary views, run time and historical > performance views along) mainly look into the performance issues and > more alligns towards the functional part of the application , > understands the database design working closely with Application > Development team and they have read only access to the databases. They > are expert in reading query execution path and have privilege to run the > explain command, reading sqlmonitor report, creating profiles, baselines > , adding hints to the query by understanding inefficient execution path, > fetching AWR report, tracing sql queries, gathering object statistics, > accessing OEM(oracle enterprise manager ) to monitor performance. > Suggesting appropriate indexes and partitioning strategies for tables etc. > > Now that we are moving few of the applications to Postgres on-premise > database and few to aws RDS postgres. What kind of privileges should we > provide to these two groups? Mainly we don't want the performance guys > to have the elevated privileges. I can understand , readonly access to > the table is something we can give to those users. Apart from that, are > there any specific privileges which we should provide,  so as to enable > look and debug into all types of performance issues without any > obstruction and at the same time not giving elevated privileges? Read: https://www.postgresql.org/docs/current/predefined-roles.html > > Regards > Veem -- Adrian Klaver adrian.klaver@aklaver.com