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 1rymYD-000R3O-0J for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 05:49:13 +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 1rymYA-00HVl9-G5 for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 05:49:10 +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 1rymYA-00HVky-5N for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 05:49:10 +0000 Received: from mail-pf1-x42b.google.com ([2607:f8b0:4864:20::42b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rymY3-0041Vb-Ha for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 05:49:08 +0000 Received: by mail-pf1-x42b.google.com with SMTP id d2e1a72fcca58-6f28bb6d747so715263b3a.3 for ; Sun, 21 Apr 2024 22:49:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713764942; x=1714369742; 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=25xhxn39xK5O4nQsAUvGUs2/t9XVg0kfk2KMzl+g5JE=; b=WmQM6r0j+dRf815CaMCxOWWqs0m5oXMrB6kD/t2qcG4SABcBPcrjKdx21Cp5t1W1nd YJD890LwDO05+g5fvDZEvKQUiFaVwEyjyaeDgY5AFsXXgmvVjqoYmh1SXMnYZUy/BRuA D3YJ3Z7+irmD8ODMoiGtnomvJwpprZd8ZL1KsuIJ2+4Wz4BGaIiFg10th7c5iIigUR1f ZmIRlGMrQK7GsZpA9luDQl5A1tQCeFxWkBEOxJPQ+r+ncExeF/AO24uf9CE7o+xpiY+/ bTlK0jRqvj5cA/GWTVa5LNfIy7SCv3DBkX6XgF9Ee/CJu88LnoLzKBS5sATnnX/IdItg u6Gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713764942; x=1714369742; 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=25xhxn39xK5O4nQsAUvGUs2/t9XVg0kfk2KMzl+g5JE=; b=c5cuY4r6qvC4hvOwC9K9yvw7YfMQZn0zeq8eVN0ZF1vZ57krrtAExENAftq6JmgCGu aif6qHlCwiKUtjMPTJ93UR4hL5VzUe/wtn+ueu7jBbWAv2l60pitlFA2t2/8biYNukI5 9QM1FD/Xs8IlotNy3Zu6votLYOUf7fgUgeNl0xVLigN2HEjE4L/WamTsM2/vqkUKHdAN t2LnzxwwniRgnEAsRWsvcmS+/d1Y0pEf8kab2Cpo04grCzxbFe/0Wj1f6qcUioC8ZbZT TDp3YBzzUrQAJlrAzOyWaaE7yPuc5R/AcyU7XXXAQHKEXntw25fVvnF6J9gMsJJf4tgz y88A== X-Forwarded-Encrypted: i=1; AJvYcCU+uwV6etD6zrHnYnZQnXDv3t8Iw6CI8nefUMZsBG4Qe7u54Hi6OlZfczhXaOzl7nFK3ECyJHljcWOzLujxU/f9NSIRObosFJx07pAMOBrZ7jLS X-Gm-Message-State: AOJu0YxQXluJoG1esyXUZ6H8OhsrGjvZpJ4hPn6SZXt3PHzerLdZBAOV q+W+VAMLF4BB4xE6PXXnUG6RDhp58Iq5IcXZJFvKktdByBkXWz+iS5ymIJe7QAws8DVpP1CbLC9 0fSmgwPI7rJScfUK3ZZXtjF/J7ew= X-Google-Smtp-Source: AGHT+IEOSKZxn/kTWms62iVsH8NvjFOWHMsZlpUBrH/32WSMF3y/MMAKjZW+4B/PZAQ8Sjo4zIBjFkJaKpMM2WC6ofA= X-Received: by 2002:a05:6a21:3e01:b0:1a7:6262:1dd1 with SMTP id bk1-20020a056a213e0100b001a762621dd1mr7931191pzc.51.1713764942462; Sun, 21 Apr 2024 22:49:02 -0700 (PDT) MIME-Version: 1.0 References: <66c140d1-e259-4684-8951-a91313d61493@aklaver.com> In-Reply-To: From: Saksham Joshi Date: Mon, 22 Apr 2024 11:18:51 +0530 Message-ID: Subject: Re: Not able to grant access on pg_signal_backend on azure flexible server To: "David G. Johnston" Cc: Adrian Klaver , pgsql-general@lists.postgresql.org, bageshkumarbagimsbi@gmail.com Content-Type: multipart/alternative; boundary="0000000000009fc62b0616a8fe29" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009fc62b0616a8fe29 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi David, We have tried granting it with our admin user also but no avail. On Mon, 22 Apr 2024, 10:50 David G. Johnston, wrote: > On Sunday, April 21, 2024, Saksham Joshi wrote= : > >> 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". >> > > Probably you haven=E2=80=99t granted pg_signal_backend to whichever role = you are > executing the above grant command with. One cannot grant what one does n= ot > have themselves, with the admin option. > > David J. > > --0000000000009fc62b0616a8fe29 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi David,
We have tried granting it with= our admin user also but no avail.

On Mon, 22 Apr 2024, 10:50 David G.= Johnston, <david.g.johnst= on@gmail.com> wrote:
On Sund= ay, April 21, 2024, Saksham Joshi <sakshamjoshi64@gmail.com>= ; wrote:
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( "GRAN= T pg_signal_backend To "our_admin_user") successfully with our ad= min user but that's not the case with postgresql 16 we keep getting the= error=C2=A0message=C2=A0 'permission denied to grant role "pg_sig= nal_backend".

Probab= ly you haven=E2=80=99t granted pg_signal_backend to whichever role you are = executing the above grant command with.=C2=A0 One cannot grant what one doe= s not have themselves, with the admin option.

Davi= d J.

--0000000000009fc62b0616a8fe29--