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 1rymuY-000Ta3-4A for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 06:12:18 +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 1rymuW-0002T1-2K for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 06:12:16 +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 1rymuV-0002Sr-L4 for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 06:12:15 +0000 Received: from mail-oo1-xc2b.google.com ([2607:f8b0:4864:20::c2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rymuS-0041fE-9W for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 06:12:14 +0000 Received: by mail-oo1-xc2b.google.com with SMTP id 006d021491bc7-5acfba298d5so1637328eaf.2 for ; Sun, 21 Apr 2024 23:12:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713766331; x=1714371131; 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=Xh6nV/PlbM2IcTDZ7xbkWsRZ+m3Z+eTzUcufzWK0HFQ=; b=Si5E1X/K8EAVSlTpz16wC0dL94EVsntlX0RB7Kfv9/KHYltoaJMg2cQbL4AmcizICQ jXiUwZtRdtWMGLl9JklCj4/trakQ9H3wOj1wIgE31YXy9Q3pXWzx7Yuzp3ZOUfMER8vk pMN8cb43SIkZ7zzVSl4DnjL5L2ZurCxt3G0Tdg/BStz4SM1AsjCzlWmtX+ixaL5rz2I4 qj+167jHwDTiVZtKdRGLUYqq069jR36kM6qk2Dr2P8Tgv3NiitQgcCV+757r88ynnW5/ ArBvcaQkvdRcxQAeHs18JRiSYo6ltXxyolJKAwGpd30BBjlcnDX4NxGxT7bWZnUaWWRV XwsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713766331; x=1714371131; 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=Xh6nV/PlbM2IcTDZ7xbkWsRZ+m3Z+eTzUcufzWK0HFQ=; b=t7AflZwhThPqSgqt7NOvZgZRyQApdJadR+4ANVllXptOoQO88amoBehbULhy6yivE3 pCgli6Ovad5+8ylzQRqkhHuZ/7nNFhTFBbSAy8TTHLw6EVugFNEylXaNQiaBTBodw49K rGeZceLr5GajTekVexwc/UmiydZMJfDu5FX/TckzpTLG9A+jBS+N9zFPbdgwnJzblxat Yq2T8yCjkKVcEnItPa3lHWOBPUXGLy49ZajoBTp9CNmf0k7qts8bz3Cl3pwkNI/uuC7D ZeaorEzNfqMfUkEo1pfuTJQQzZpWrNVB65zHgXBX+IO6j7lXgoiQJHc4lgFSwRoOc+PJ XNJA== X-Forwarded-Encrypted: i=1; AJvYcCVlYGw2tubwm1hQTkmzfNbCZKAfoTqpvbcGdL72usUZOah369N8Qx9y14gFi+zRP/yB62fqd+OamuiwdBtL1yF9TGYxuUodTY15P3aHiketa1kI X-Gm-Message-State: AOJu0YwncfiqDop2EZPuS3P8RUc2A/UrIjmiY7RofsLzVYqZSYQCbEnp so99QJALc7tJwGAKxSqj71MFrxxBC4OpmJetolzX8r+mKFpNF+LMn2jw96bkcv44sW9R90KwBY6 UAOhESoLJaAvB5q7pVb0YOfNdtRs= X-Google-Smtp-Source: AGHT+IEPCGCDptGUP9ZrGfvlM+p8egWwABkQ4zIFJeeZyUlevzpcqaqFHoYW0SKtobuphp1/q59j2gPpkVBoqn6eyv8= X-Received: by 2002:a4a:942:0:b0:5aa:492a:4a6d with SMTP id 63-20020a4a0942000000b005aa492a4a6dmr9546097ooa.2.1713766331491; Sun, 21 Apr 2024 23:12:11 -0700 (PDT) MIME-Version: 1.0 References: <66c140d1-e259-4684-8951-a91313d61493@aklaver.com> In-Reply-To: From: "David G. Johnston" Date: Sun, 21 Apr 2024 23:11:35 -0700 Message-ID: Subject: Re: Not able to grant access on pg_signal_backend on azure flexible server To: Saksham Joshi Cc: Adrian Klaver , pgsql-general@lists.postgresql.org, bageshkumarbagimsbi@gmail.com Content-Type: multipart/alternative; boundary="0000000000006aab690616a95164" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006aab690616a95164 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Apr 21, 2024 at 10:49=E2=80=AFPM Saksham Joshi wrote: > We have tried granting it with our admin user also but no avail. > This is how v16+ works in a community installation: postgres=3D1 # create role cr createrole; CREATE ROLE postgres 2=3D# set role cr; SET postgres 2=3D> create role otherrole; CREATE ROLE postgres 2=3D> grant pg_signal_backend to otherrole; ERROR: permission denied to grant role "pg_signal_backend" DETAIL: Only roles with the ADMIN option on role "pg_signal_backend" may grant this role. postgres 1=3D# grant pg_signal_backend to cr with admin option; GRANT ROLE postgres 2=3D> grant pg_signal_backend to otherrole; GRANT ROLE David J. --0000000000006aab690616a95164 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Apr 21, 2024 at 10:49=E2=80=AFPM Saksham Joshi <= ;sakshamjoshi64@gmail.com&g= t; wrote:
We ha= ve tried granting it with our admin user also but no avail.

This=C2=A0is how v16+ works in a community insta= llation:

postgres=3D1 # create role cr createrole;
= CREATE ROLE

postgres 2=3D# set role cr;
SET
=
postgres 2=3D> create role otherrole;
CREATE ROLE
postgres 2= =3D> grant pg_signal_backend to otherrole;
ERROR: =C2=A0permission de= nied to grant role "pg_signal_backend"
DETAIL: =C2=A0Only role= s with the ADMIN option on role "pg_signal_backend" may grant thi= s role.

postgres 1=3D# grant p= g_signal_backend to cr with admin option;
GRANT ROLE

postgres 2=3D> grant pg_signal_bac= kend to otherrole;
GRANT ROLE

David J.

--0000000000006aab690616a95164--