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 1rym67-000P8b-1F for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 05:20:11 +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 1rym65-00HRGb-9n for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 05:20:09 +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 1rym64-00HRGN-V1 for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 05:20:08 +0000 Received: from mail-oo1-xc2e.google.com ([2607:f8b0:4864:20::c2e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rym62-0041LB-ES for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 05:20:07 +0000 Received: by mail-oo1-xc2e.google.com with SMTP id 006d021491bc7-5aa28cde736so2535358eaf.1 for ; Sun, 21 Apr 2024 22:20:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713763206; x=1714368006; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=U54vMS8yI/n2zKgWAFGVjbshXpZp/oKI6VzszyDt3Pg=; b=MPGCriT+tB7buNmdlt+t6mLBYovAH3R/jMmQVywLSVdC4ww7au+Dnr6HE/mq98rJgD 5rxR0fnRzdtlHBIUW4ZMVGC7Hp8yIwtvDZud/O49pyp7efn+184ww6u6qPyM6h38mD1B eeeo5m0b+Ajz4FSb6VZnbiWJtrzr41T8jszK3cKo05KfSzUt9hFOB1Ng0/Hb3jhNb/KK H7qOrNKpDDmrU2VjIfLaUT5ptsugKIvll//nSyqF6Rx2OE6wIr7+yLK0AdQMV5XuBffX X8xxJ5Vy2yhQ8ka5+A/bxLJYhUQiJ3T36zT2D7nlf8UaTNO2iD10Dn+ptn8FCVM5xbmf w1LQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713763206; x=1714368006; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=U54vMS8yI/n2zKgWAFGVjbshXpZp/oKI6VzszyDt3Pg=; b=VL5ZVg04A0NJbOP7qEtUoPaTwS5YHW5XnpjMx2Inibe9pvstUwH/bowyahNBxPbDSE jKYSUfiIbQWGdX5at5tJC6gXGo5B46Uub1XVK/LghaKbwNqc6WSib00HjiZP7+RXYs6Z Ysna9oamliG1hGIH9azaN4bNML8bQKBuYQD29OC5dMzzQyKaBnLvXvlfTU+fGcrQaUkz 0R5mKibEsEmYAtZCEImHmA3PNjdtetZ6w9k4t97uA2jXteNS82ZbMJaLqDzDid4uOcm6 jMNvq3rXn9RNIeBlbHgGjP/b4BgMNTdY8BABa9PAHxrnpT3LEvGitO7+xQtWoKJE3wA1 4Hcw== X-Forwarded-Encrypted: i=1; AJvYcCUqCxy9D0hslUQaJJ9RZVAgea0+WwZFf8TtBtFoYtcHU5YFKifN5xvAgd5nhwf01F4BpEb7VM1JRC7dFeXuQO8Rn2u8MH3sSjc2LECuBHHq1c44 X-Gm-Message-State: AOJu0Yy7m6LTxqr0sIzY5pb8pTGovM+QDuTUQ/1EA7pBmtds1xXGLVXo R3BzdQeStdzyuGE6TUAcg230Cta+df/PVtaFOMhWttp2oePGBEMd+hU091vjLlEthF/9HrRHi6U e4RLLVKCPZmfMQllR4LhmgA4yjz4= X-Google-Smtp-Source: AGHT+IGNnddksYnVjskra42TqO56nrX+eI48XPvOlw9yrrjMiHlxPkpU3lku1+qhwWNvzS7aDQWvQ7Rtv6u/10SP/bc= X-Received: by 2002:a4a:5892:0:b0:5a4:aea7:8066 with SMTP id f140-20020a4a5892000000b005a4aea78066mr11241478oob.5.1713763205761; Sun, 21 Apr 2024 22:20:05 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a8a:d96:0:b0:525:bd21:4d70 with HTTP; Sun, 21 Apr 2024 22:20:05 -0700 (PDT) In-Reply-To: References: <66c140d1-e259-4684-8951-a91313d61493@aklaver.com> From: "David G. Johnston" Date: Sun, 21 Apr 2024 22:20:05 -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="0000000000001bd15d0616a8971b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001bd15d0616a8971b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 b= ut > 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 yo= u are executing the above grant command with. One cannot grant what one does not have themselves, with the admin option. David J. --0000000000001bd15d0616a8971b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sunday, April 21, 2024, Saksham Joshi <sakshamjoshi64@gmail.com> wrote:
Hi,
I am afraid that&= #39;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 t= he case with postgresql 16 we keep getting the error=C2=A0message=C2=A0 = 9;permission denied to grant role "pg_signal_backend".

Probably you haven=E2=80=99t grante= d pg_signal_backend to whichever role you are executing the above grant com= mand with.=C2=A0 One cannot grant what one does not have themselves, with t= he admin option.

David J.

--0000000000001bd15d0616a8971b--