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 1rylx1-000OUu-PF for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 05:10:47 +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 1rylwz-00HNvP-DG for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 05:10:45 +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 1rylwz-00HNv8-0K for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 05:10:45 +0000 Received: from mail-pj1-x102f.google.com ([2607:f8b0:4864:20::102f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rylww-0041Gg-92 for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 05:10:43 +0000 Received: by mail-pj1-x102f.google.com with SMTP id 98e67ed59e1d1-2a6fa7773d3so3211610a91.3 for ; Sun, 21 Apr 2024 22:10:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713762641; x=1714367441; 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=hlRjNN+noi7lrEspuXzKETMjWlKRK6LCOrPhmI+lhZs=; b=blZ+2iCLcEaBm33VlL9sHg08LaHD2DUgpwmnTmmRxY/dJr+yEC/RiO+7vwPikK+UtE 0hcgePK3wOFAOKFXZ1tMsnfe97hOuRZ2jQHvYh2RYMAlGTIXG+qHiuVKQX6J4osHj/A4 3zL5K5HELMzBemhci4Ese024S1lTHqvs+gsRa4Pdzfn5aVopb/Zgo8Pr0Ves1hpEZvue kM6SrWTrgJd6HqinQUYcvmFUwucauVl78V+yhY02F0ROT00QtkvnVmUh0tJp2jpz2myD TSBLUcSnhQENI7zX/XK1hYGuxd5+Q1h1SXB06S8OcpoNfIWWF5KT6JDzXtE7IE5Hxjph Pmqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713762641; x=1714367441; 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=hlRjNN+noi7lrEspuXzKETMjWlKRK6LCOrPhmI+lhZs=; b=EyMxTPXa0sYTFiPR4GESxBDhPs0xPkfNsFui3Tna9n06Sf7FVK8nLWq+S8LZGYjMWR vSDy3LEREvcK9VsrqAjleRS4fKC5RwLNNI2IUI4sKKk+WCDvmEbC9gHRRoSA5hdZlpLU 0Kz6GEYGKY49EzJciPocefuaCEgkJtLtYDbbY31Nmbbr7Is1FNM/RGDxDF6N/Q0wc3t/ KhfmwiGlWx1K4LePRXr1zMe4sobcJRHgXQ1klro9NVhRu94cua/nEVAH4BmjFml5G3eY WYnDhmofZFJPviPUSG95n7131TybS/zv+MEW0BSkZQGbgZ11pdxpgPcu+E2L9NrNLulw 6lNQ== X-Gm-Message-State: AOJu0YxI8jM5uGkSlQTGjU1WYXvwfD0r7TTRUg8l6KzGUX29bHG+aj9v Wr2vL6Zbj7R7xwo9CQaiAxwVa5/SoeiJ82M0MbDO7VLtlTiekPHgZn4U6Md+sHCq2mtTU+OYxdK VtnNI80DUWy5cPXWM601QnocpPAw= X-Google-Smtp-Source: AGHT+IHve90C/lRgvV9y+RLY/LGGW2yR3bHqDVAfr6bg/FOfWUrbMBGCXahLwt0S+JR4AJc9hhYOcu+RM/440UoKBVM= X-Received: by 2002:a17:90a:fe98:b0:2a4:833f:2c1b with SMTP id co24-20020a17090afe9800b002a4833f2c1bmr7537101pjb.9.1713762641141; Sun, 21 Apr 2024 22:10:41 -0700 (PDT) MIME-Version: 1.0 References: <66c140d1-e259-4684-8951-a91313d61493@aklaver.com> In-Reply-To: <66c140d1-e259-4684-8951-a91313d61493@aklaver.com> From: Saksham Joshi Date: Mon, 22 Apr 2024 10:40:24 +0530 Message-ID: Subject: Re: Not able to grant access on pg_signal_backend on azure flexible server To: Adrian Klaver Cc: pgsql-general@lists.postgresql.org, bageshkumarbagimsbi@gmail.com Content-Type: multipart/alternative; boundary="0000000000007465e50616a8757f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007465e50616a8757f Content-Type: text/plain; charset="UTF-8" Hi, I am afraid that's not the case with postgresql 16 since we also tested with postgresql 15 we are able to run this command( "GRANT pg_signal_backend To "our_admin_user") successfully with our admin user but that's not the case with postgresql 16 we keep getting the error message 'permission denied to grant role "pg_signal_backend".Also,In postgre 16 only the current users of the database are able to close the connections.Can you help on this please? On Fri, 19 Apr 2024, 19:50 Adrian Klaver, wrote: > On 4/18/24 22:48, Saksham Joshi wrote: > > Hi, > > We have created an azure postgresql flexible server and we have added an > > ad admin as a user and Created our database using this admin > > user.However,When are running this command: 'Grant pg_signal_backend To > > adminUser' we are getting an error that says 'permission denied to grant > > role "pg_signal_backend".While this is strange the admin user is infact > > the owner of the said database and we don't have any other user that > > have the said privileges. > > > https://www.postgresql.org/docs/current/predefined-roles.html > > "PostgreSQL provides a set of predefined roles that provide access to > certain, commonly needed, privileged capabilities and information. > Administrators (including roles that have the CREATEROLE privilege) can > GRANT these roles to users and/or other roles in their environment, > providing those users with access to the specified capabilities and > information." > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > --0000000000007465e50616a8757f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
I am afraid that's not the = case with postgresql 16 since we also tested with postgresql 15 we are able= to run this command( "GRANT pg_signal_backend To "our_admin_user= ") successfully with our admin user but that's not the case with p= ostgresql 16 we keep getting the error=C2=A0message=C2=A0 'permission d= enied to grant role "pg_signal_backend".Also,In postgre 16 only t= he current users of the database are able to close the connections.Can you = help on=C2=A0this please?

On Fri, 19 Apr 2024, 19:50 Adrian Klaver, <adrian.klaver@aklaver.com> = wrote:
On 4/18/24 22:48, Saksham Jo= shi wrote:
> Hi,
> We have created an azure postgresql flexible server and we have added = an
> ad admin as a user and Created our database using this admin
> user.However,When are running this command: 'Grant pg_signal_backe= nd To
> adminUser' we are getting an error that says 'permission denie= d to grant
> role "pg_signal_backend".While this is strange the admin use= r is infact
> the owner of the said database and we don't have any other user th= at
> have the said privileges.


https://www.postgresql.org/d= ocs/current/predefined-roles.html

"PostgreSQL provides a set of predefined roles that provide access to =
certain, commonly needed, privileged capabilities and information.
Administrators (including roles that have the CREATEROLE privilege) can GRANT these roles to users and/or other roles in their environment,
providing those users with access to the specified capabilities and
information."




--
Adrian Klaver
adrian.klaver@aklaver.com

--0000000000007465e50616a8757f--