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 1qfsR1-00DThF-UA for pgsql-novice@arkaria.postgresql.org; Tue, 12 Sep 2023 01:43:23 +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 1qfsR0-004DCM-MZ for pgsql-novice@arkaria.postgresql.org; Tue, 12 Sep 2023 01:43:22 +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 1qfsR0-004DBy-BV for pgsql-novice@lists.postgresql.org; Tue, 12 Sep 2023 01:43:22 +0000 Received: from mail-oi1-x22c.google.com ([2607:f8b0:4864:20::22c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qfsQv-004Yfk-DL for pgsql-novice@lists.postgresql.org; Tue, 12 Sep 2023 01:43:21 +0000 Received: by mail-oi1-x22c.google.com with SMTP id 5614622812f47-3a751d2e6ecso3944588b6e.0 for ; Mon, 11 Sep 2023 18:43:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694482995; x=1695087795; 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=so7bvZufvq6gMOKxzZXUZo7jGjWyOrVR3j5WrOQUeCk=; b=X3CqPGVhXun+icOMbV3Q8wwBsOEirsqUHRCF//QHdvRjirSaJwrTWz86fQLqQ5T5I1 Hct03+A0Xlsqfa/QxiV3C/dPdpCRtYGerDudtiYb9TOmfW9y5zcgsxuNuPrVxF0C91C9 oLXbtuaqYtsptIz8WIdWglpu8dQSlT5XVzza0arD5dgn0z8ITcIr+baLD8NvIjIlItBh wNt99yKZTI/Ne7fdqvjkXxX00gEmegx9B1oyQvfR2WMiEOsmFucOf44LjmxOmvPW/3II nnNkqbZp9Oga+uApbmpBz8p29zzbXxAcfafEAjgr3pK07Xj7ecFGGezuhilOul3PAh/L o/3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694482995; x=1695087795; 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=so7bvZufvq6gMOKxzZXUZo7jGjWyOrVR3j5WrOQUeCk=; b=s4UzrfIGUgqYruWfUsX+M3DenGQdzZLmPX++l8btdUzugoDw18tT5ACx8JFiwr+FWg ljgsh2piYWXEOhb1MRSotECFt1DF/92M3oECgXVG1BJBnFrNRCspTRnECyRFk1YcnzvB 5P0V5e0tE4iliu/emALX2rQUwGf9Z36LcV/HCuG5LJLc8CrO+blqZPE4pVth3H+MaOb7 YVJ5ikgf4xeS6JhZZ8e5Iiga/5fMb1xGiBY5IQd48xckw7XQKtA47+EiS9Qe8bacixVo 5SND5AmhgRfSbf04SV1+7z2gM4nAPvXi2PcwCw7faAz/6K/M4VHnmhYNR3vxscJ3m0Ae Cr2A== X-Gm-Message-State: AOJu0YzZCA3x7HQacIls+3JHQDuZ6BEZ30aFQ12hW6kj3y20mBeolngo U1lnucnQNm8pe1+QOx6u5J5FSpyNXYrMFZfSac0= X-Google-Smtp-Source: AGHT+IEi/ha8aR+elW3xoGXs/sIDTBXAjsK3IdKxAmYBJZgVHxeePm1VxnOMpiy6mabKUkm+A+DKUFMZ2AQhoZH13fw= X-Received: by 2002:aca:2803:0:b0:3a8:43d5:878b with SMTP id 3-20020aca2803000000b003a843d5878bmr11833730oix.2.1694482994629; Mon, 11 Sep 2023 18:43:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Mon, 11 Sep 2023 18:42:56 -0700 Message-ID: Subject: Re: Grant CREATE privilege on all schemas To: ivanov17@riseup.net Cc: pgsql-novice@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000f9109d06051f909c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f9109d06051f909c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Sep 11, 2023 at 6:05=E2=80=AFPM wrote: > But I can't set permissions for > databases and schemas that haven't been created yet. There are default privileges that can be setup so that when new objects are created existing roles are given the described grants at that time. https://www.postgresql.org/docs/current/sql-alterdefaultprivileges.html Note the absence of DATABASE as an object type on that page. > Or maybe there is > another way to organize the process of migrating multiple databases? > > And finally, where it would better to create a feature request? There really isn't such a thing as "feature request" here - there isn't anyone that really makes it a point to fulfill such requests and there is more than manageable work in process already. That said, discussion about what PostgreSQL can and cannot do, sent to the -general list, do get read by many including developers. David J. --000000000000f9109d06051f909c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Sep 11, 2023 at 6:05=E2=80=AFPM <ivanov17@riseup.net> wrote:
But I can't set permissions for
databases and schemas that haven't been created yet.
<= br>
There are default privileges that can be setup so that whe= n new objects are created existing roles are given the described grants at = that time.

https://www.postgresql.org/docs/cu= rrent/sql-alterdefaultprivileges.html

Note t= he absence of DATABASE as an object type on that page.
=C2=A0
Or maybe there is
another way to organize the process of migrating multiple databases?

And finally, where it would better to create a feature request?

There really isn't such a thing as "featur= e request" here - there isn't anyone that really makes=C2=A0it a p= oint to fulfill such requests and there=C2=A0is more than manageable work i= n process=C2=A0already.=C2=A0 That said, discussion about what PostgreSQL c= an and cannot do, sent to the -general list, do get read by many including = developers.

David J.

--000000000000f9109d06051f909c--