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 1ryoOA-000cXP-79 for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 07:46: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 1ryoO8-000Q4r-T8 for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 07:46:56 +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 1rynzD-000I9o-IO for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 07:21:11 +0000 Received: from mail-lf1-x134.google.com ([2a00:1450:4864:20::134]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rynzB-002INT-Om for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 07:21:10 +0000 Received: by mail-lf1-x134.google.com with SMTP id 2adb3069b0e04-518a3e0d2ecso6011095e87.3 for ; Mon, 22 Apr 2024 00:21:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713770467; x=1714375267; 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=s8LyaPwwvNIBu/Pb+bw7Bn4vejMZSMzKba5pT/fQ7oM=; b=aFBESC11BDNY2ubIbpBscjLU1CZqJVNtiYTPjKHd57aopYJucvd34aRJtQiAtqQJrw LDtkCzxkQg8cbkjnnIiht9sG1WhjvOXmC9utskEXvXBtD/jjepertGHSWnTlVU3WnCzk ezSmoaQTollt13qEdxA9eiUCAaowuFYe2Vi26/S2m8GXrqbi5GJOpakibTtKlU6fcs5X c4a9nzrAce4LuDXyEOOM2nHycW5onechnaDjFVysllolrgLw/pfetBTxeIGeqZAVZtMw SIzIQUMISC7xj9xqCCGYMaX5NvZM03lOA+WGekzVyd6nc0TEsJNiNVT0JAbbKNH8G6Jv TzPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713770467; x=1714375267; 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=s8LyaPwwvNIBu/Pb+bw7Bn4vejMZSMzKba5pT/fQ7oM=; b=qkRShQc4I82TwFpf7ZfYg0i9ZNEsnZBbc8H9JXp8+PbIXIiyiXOShP5ykti3g7/plL TIE+5U7jPNTcY8xbHn8JrQ/lGQenJ03UF0O4D3b2a9Yx4JUsnFgQ2Huyxpohj6E3pTCt Hl8orsiKAe/xp631S1uDibULtJKOU2z2r/HGSTxGoSZblPtZxiNwNzx6RyaApgNFjD00 piupoDE83aeUCWpgi+Omk7n6jktA4emZQUGGyquievbXZPMZdMeh9bMyBxlO7u7Wkbl4 BuggGt4Cjnc7zSvPmqGHwyjn8Ru+r0Fb39bcbYPBOFBbEHQ+MO/EeUH4N/2Z1l1457Jf 3yjw== X-Forwarded-Encrypted: i=1; AJvYcCWIWO+g0t4T/L/qEkDBNCu1SBYyhCc+aAN38GBhUFY2FnGPpss/hnr4oNN9EBMpvWuff6dSlfViTl/WhmUMMP81AIaaCOpDrbZYdhcTzO9NmeFJ X-Gm-Message-State: AOJu0Ywjtz8k3Y8wHYm97LysZC16pYZaMZe1ahxu9OdlLKHnFU5Hw/fo q8+Pbd7PPvk9Dks/FLpkvI3859Qhi7i33JOsQgaPTH0GHTNPE4HE+9nqsjH1vjX1EbmEkuYiZFb zA9eNCRyl2ubqTsMEfRPVIkDnpZU= X-Google-Smtp-Source: AGHT+IELfTSupYQeBYkmG/QNqngTKBaxVTcfjzYwDb0zK3ypk3iYdhHzp6nzVwkOAjY/G6tEXfQhv86q6QE6CK6DB7s= X-Received: by 2002:a05:6512:39c9:b0:518:d5c4:d9b7 with SMTP id k9-20020a05651239c900b00518d5c4d9b7mr7683919lfu.16.1713770467339; Mon, 22 Apr 2024 00:21:07 -0700 (PDT) MIME-Version: 1.0 References: <66c140d1-e259-4684-8951-a91313d61493@aklaver.com> In-Reply-To: From: Bagesh Kumar Singh Date: Mon, 22 Apr 2024 12:50:55 +0530 Message-ID: Subject: Re: Not able to grant access on pg_signal_backend on azure flexible server To: "David G. Johnston" Cc: Saksham Joshi , Adrian Klaver , pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000eeb6ab0616aa4776" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000eeb6ab0616aa4776 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable No luck. On Mon, 22 Apr, 2024, 11:42=E2=80=AFam David G. Johnston, < david.g.johnston@gmail.com> wrote: > 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. > > --000000000000eeb6ab0616aa4776 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
No luck.=C2=A0

On Mon, 22 Apr, 2024, 11:42=E2=80=AFam Davi= d G. Johnston, <david.g.jo= hnston@gmail.com> wrote:
On Sun, Apr 21, 2024 at 10:49=E2=80=AFPM Saksham Joshi <sakshamjoshi64@gmail.com> wrote:
We have tried granting it with our admin user = also but no avail.

This=C2=A0is h= ow v16+ works in a community installation:

postgres=3D= 1 # create role cr createrole;
CREATE ROLE

post= gres 2=3D# set role cr;
SET

postgres 2=3D> create role otherro= le;
CREATE ROLE
postgres 2=3D> grant pg_signal_backend to otherrol= e;
ERROR: =C2=A0permission denied to grant role "pg_signal_backend&= quot;
DETAIL: =C2=A0Only roles with the ADMIN option on role "pg_si= gnal_backend" may grant this role.

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

postg= res 2=3D> grant pg_signal_backend to otherrole;
GRANT ROLE

David J.

--000000000000eeb6ab0616aa4776--