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 1uGjVr-006aJ1-Ob for pgsql-general@arkaria.postgresql.org; Sun, 18 May 2025 19:17:32 +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 1uGjVq-00BMfM-4s for pgsql-general@arkaria.postgresql.org; Sun, 18 May 2025 19:17:30 +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 1uGjVp-00BMfC-MX for pgsql-general@lists.postgresql.org; Sun, 18 May 2025 19:17:29 +0000 Received: from mail-ed1-x52a.google.com ([2a00:1450:4864:20::52a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uGjVn-002R9e-0h for pgsql-general@lists.postgresql.org; Sun, 18 May 2025 19:17:28 +0000 Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-6016d401501so3617773a12.2 for ; Sun, 18 May 2025 12:17:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1747595845; x=1748200645; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=HDUuF+2IE3n9RFW9e3Fg8vIgNIvxjKLY5uDAnwvTDNw=; b=TT87Oa+I/ykbyEGVvi/9T8m7rpQx2sCGsdsRX+EvzhatI5AfLmqmPc/daKljik5H7p h1mxs07zPh1wz6c0YfX62EH7EaK6mNkCMrl0IKVOglbeWzPolG+ZQ7ni8XYb1co+Zqc3 XWyE6fXLjgcV/gi0+aGfQEMKg4/DxKM4IjhI3TC1SVPQfepFBwjeDwplNcRMB1X7Sz7M oucCiDnUv6Cw+7L0H1f0fpKl//wKl9ruysLWc4oy8fp8DT63vrWcIkyjJ+DRwvevQXH2 fd92+dfadxEzqWBJDIJPigEEcn+qWE4mA+a/jNk2F54/xEvSrx6nMeIfawU0i7o+xkss BaAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747595845; x=1748200645; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=HDUuF+2IE3n9RFW9e3Fg8vIgNIvxjKLY5uDAnwvTDNw=; b=OAk81JPNYa+hRfhJKZWKkMYFY5E8HGBZgOKA4R/F/gEad/YbArqbFkmDJA8tP7Af3H /4ajsrl16KLbKKdK/Tqet7/mzkJyxW/4jBptJjPPbQPAVPwqFsVyaNKYHfBZOjFbxqOI 9drv8DhYqwhSC2Pqw8HxevtSnf7wjkgBlYbjv4Q/gYnAFlyK2utai+a6OkvMe/y4t/Rn dUEeQQNwPGVoSkiVNaGPjOFcWDXrJ70rOaEJDc8fkxDyXMbCj7qR+wL5OM1faPG3xlLm ixo2m6j/B0ARloWunzqErtsL6ZRmBKVLIFzhHqKl/FNJ+4IgvV5JO7yytYca1rvIYqro CdqA== X-Gm-Message-State: AOJu0YwXhYXC+1GS/YrTzbNhIF9o1AXs2EU90eEKX3gtN+y3jHT9fl5f wHmjNzzry7fWBeKTQ4Ix+4Pn7Ua1hmeudkRjE5Ac376hmzy8YWKTQjfQTqxBiM15PR34twF4T6S e+6tWEItqg9yTVuaGgdCEug9/8luMosfTeaPn X-Gm-Gg: ASbGncsf+GEz0dvwFnTE7Zd5fSwzcT9xg0RRFZ1sX4p8/E+02FOxQBWnS8bUmN30C/W xsKXGBMbPwbHFhAw+5Mr4Xzzed9BMcVdgdEpmRAcpla1kCaBbuX3wUHuHE5TF2IW3t58Svoloxp 2UY1ajOvw7ol/fuz1dJ31BBESeJW6JKg== X-Google-Smtp-Source: AGHT+IF1rNejtnsqWDlsJL5IxI9TiUlDG+iuxVSdYDEHqvCXt/10V7vFVE7thLC2uHtQGHrJd2ZMURDgW85gjGGHvBQ= X-Received: by 2002:a05:6402:40c5:b0:601:e0e1:825b with SMTP id 4fb4d7f45d1cf-601e0e1844cmr1912296a12.3.1747595845257; Sun, 18 May 2025 12:17:25 -0700 (PDT) MIME-Version: 1.0 From: Ayush Vatsa Date: Mon, 19 May 2025 00:47:13 +0530 X-Gm-Features: AX0GCFshpiKGpJpH-6SgLg0Ue5MTqsFF_nucdWMeaOEj5tcWLHaGmaUC9Sw3H50 Message-ID: Subject: =?UTF-8?Q?Clarification_on_REVOKE_ALL_ON_FUNCTION_=E2=80=93_Are_ther?= =?UTF-8?Q?e_any_privileges_apart_from_EXECUTE=3F?= To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000914cf006356ddde0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000914cf006356ddde0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Postgres Community, I had a quick question regarding function-level privileges in PostgreSQL. We know that REVOKE EXECUTE ON FUNCTION ... removes the ability to call the function. But when we do: REVOKE ALL ON FUNCTION my_func(args) FROM some_role; does this revoke anything other than EXECUTE? Are there any other privileges that apply to functions which get revoked via REVOKE ALL? I looked through the documentation but couldn=E2=80=99t find a definitive a= nswer on whether ALL includes more than just EXECUTE in the context of functions. Would appreciate any insights or pointers. --------------- Regards, Ayush --000000000000914cf006356ddde0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Postgres Community,
I had a quick question regardin= g function-level privileges in PostgreSQL.
We know that REV= OKE EXECUTE ON FUNCTION ... removes the ability to call the function= . But when we do:
REVOKE ALL ON FUNCTION my_func(args) FROM some_= role;

does this revoke anything other than EXECUTE? Are there any other privileges that apply to functions which get rev= oked via REVOKE ALL?

I looked through the documentation but couldn=E2=80=99t find a definitiv= e answer on whether ALL includes more than just EXECUTE<= /code> in the context of functions.

Would appreciate any insights or pointers.

---------------
Rega= rds,
Ayush

--000000000000914cf006356ddde0--