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 1tfQlk-002Kkr-Dc for pgsql-general@arkaria.postgresql.org; Tue, 04 Feb 2025 21:47:44 +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 1tfQlh-0095eY-QB for pgsql-general@arkaria.postgresql.org; Tue, 04 Feb 2025 21:47:41 +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 1tfQlh-0095eO-Ft for pgsql-general@lists.postgresql.org; Tue, 04 Feb 2025 21:47:41 +0000 Received: from mail-il1-x12a.google.com ([2607:f8b0:4864:20::12a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tfQlf-003CAT-12 for pgsql-general@lists.postgresql.org; Tue, 04 Feb 2025 21:47:40 +0000 Received: by mail-il1-x12a.google.com with SMTP id e9e14a558f8ab-3d01fe20598so14884105ab.3 for ; Tue, 04 Feb 2025 13:47:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738705659; x=1739310459; 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=+VeClYys+xpFEeXSvWnufya5JoE16/bHafP6dyJJC+Y=; b=jwGPIphHc5+HZgGBX5z43z+tYTErcqCF92zzbIgphXMq9+3Hxoxym2YMtYMTsAqN/H VUve4F/OvZwQo+JKWoRVmrSkFt1W8NW97F4qXqxEN5gwW5bdxJo9LCQCFSR/qCF0Ei4K 73qdHi1c96abliKFIb/8G3kxbqlXY8fTDyPh6FH2bqm0wTnZUMtRZpLIY5kdi0lr8j1E 3rvSpN9ijpCz9lAwhm0rHzrpDabSutGmdZ7x79xjd+93u1ZIH9fSLCfo2GvVA3bqFdhe kEuRmgoju+SH7Z+NRjfRtSiTa4YT/EmHiuDakEDBxMOfLSqEqU+aTMkp+gU/sDmO/lhb 0+HQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738705659; x=1739310459; 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=+VeClYys+xpFEeXSvWnufya5JoE16/bHafP6dyJJC+Y=; b=sGa1HPJl5mXcZnvwZHRaa/WawYzz1mW72q4Cr2Kh0kl6u1iRRN/kofB2OFhn/xixGF rioHpzlOjZNomV8exH5YosZVNY3twZiG+gMaIj3QWGLSoPSACg6YQSYrfqZTsfobpIPu R7ENuraFJmRHMMod5vbqCWEi8T4VLJq4zS4HqhV0ta8Jl71JjsK0x3epbw/jA9rZRyXK AEcTmTH7MDt9PUsnsunEKSmvCuGQczF/mTbsaIGSbjQu2IRRYyE766yjSoTO3n5jm+fF ZerlwtDJHzQPVSdIQe+ZEDWv8GyRHmNpftu4DewGAyum6tQfuNH7c7t6hC0bRk0AN8Q6 yzUA== X-Gm-Message-State: AOJu0YxArn2OpW/VUQ1chbA0Ov+ZAel3dGHJ663/2VwkNFdN46RwaZYq 0U8+5+fPUDkmq6F+ED2utNCFuqXEvzD5exgwZfAsLPZqrhOm49DBdaV6S4yZGkI36csSZcrEWk0 q5hkJQga0TpVhLu78qBXlpN2E44I= X-Gm-Gg: ASbGncuZMIQYygBXH1qTW9jVnVN5P8ir0/YOsQ/+A1t/W2/KcsfMEzfmwvvdLyXaZk2 eeufzT5jKGdKOauWdLtu+GgkFgx8n1tNyCDgZenIt/hbLfEcV21n1+QCafiJzULi/m/sNweeQO4 GvJKoB1MEwbJ9wSXU1gIBUiMjpZUxTTnU= X-Google-Smtp-Source: AGHT+IFduToI8QCBGzf+tjNnDpsG1G6PXQJruvJNTt0K8okOk/TyJu3Loj8WAA0DtEAJRN4NdwB+2GGLxPZ81LpU24g= X-Received: by 2002:a05:6e02:1c84:b0:3cf:c82f:586c with SMTP id e9e14a558f8ab-3d04f40098amr4027885ab.4.1738705658893; Tue, 04 Feb 2025 13:47:38 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Greg Sabino Mullane Date: Tue, 4 Feb 2025 16:47:02 -0500 X-Gm-Features: AWEUYZlqSRKn751hHGJGyvBjB6kYcLKgWd4S0hYDKVQWFm0Ta5e0AY2qoBCO4Wc Message-ID: Subject: Re: Understanding ALTER DEFAULT PRIVILEGES Behavior in PostgreSQL To: Ayush Vatsa Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000002ae02d062d57f5bc" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002ae02d062d57f5bc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Feb 4, 2025 at 1:50=E2=80=AFPM Ayush Vatsa wrote: > Also, what would be the best way to ensure that, by default, no roles > (except the function owner) have any privileges on new functions created = in > my protected schema? > Create them in another schema altogether, then move it to my_schema once the privs have been set. Cheers, Greg -- Crunchy Data - https://www.crunchydata.com Enterprise Postgres Software Products & Tech Support > --0000000000002ae02d062d57f5bc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Feb 4, 2025 at 1:50=E2=80=AFPM Ay= ush Vatsa <ayushvatsa1810@gm= ail.com> wrote:=C2=A0
=

Also, what would be the best way to ensure that, by default, no roles (e= xcept the function owner) have any privileges on new functions created in m= y protected schema?

Create them in another schem= a altogether, then move it to my_schema once the privs have been set.
=

Cheers,
Greg

--
C= runchy Data - https://www.crunchyda= ta.com
Enterprise Postgres Software Products & Tech Support
<= /div>
--0000000000002ae02d062d57f5bc--