Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kkXNv-0000Z5-Jw for pgsql-admin@arkaria.postgresql.org; Wed, 02 Dec 2020 19:01:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kkXNt-0000Nc-23 for pgsql-admin@arkaria.postgresql.org; Wed, 02 Dec 2020 19:01:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kkXNs-0000NU-Ok for pgsql-admin@lists.postgresql.org; Wed, 02 Dec 2020 19:01:48 +0000 Received: from mail-qk1-x736.google.com ([2607:f8b0:4864:20::736]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kkXNq-0005NZ-CN for pgsql-admin@postgresql.org; Wed, 02 Dec 2020 19:01:48 +0000 Received: by mail-qk1-x736.google.com with SMTP id z188so2286181qke.9 for ; Wed, 02 Dec 2020 11:01:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=L0D4GYnI7Y8L1r+N7MdQwpMpdwPojBXWgxjyP2UWmf8=; b=orhuwbfLv0hOj0ePX/Ka8u1GPQnfjzYwPMLIvxblukH6malzJb5jXwvUwMaouzQkgF vyJ9oUre3g6iLcoEllyGQ36Xfqwlt2kH8PuAnCDqkGUbveIGSqcEcHnFqkp8eGFvceuB jIG5D5gmL3L5qppk8ZUUB3TBDOa09xsWYTTGSXdFpBRB5XO6Q1DeaXC9j/Aw3a5Qgr7k WmOL6JCy8mywQXN6rcFSWFmLu6sBrSpI9KbsQ0K0PEU7Z1u9SMdl30YR9WK0S1COX+4Q x3WoiTh19QT96KueXooK74omSTHNPXV6/WhOVUyvvMT+0g9Cp9fNIGotJDnjuuQwFlsf SKbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=L0D4GYnI7Y8L1r+N7MdQwpMpdwPojBXWgxjyP2UWmf8=; b=gfT7iwqHSe/HkTPB4ajh/wGiIWVSx8tiyMCieJVd9QCpfIrm86W5BjcGEEOf6rb01k BIw/HCq7UHk9plPVtSHQRpQeq8SuAITSXI6GvBVEh+cukoq1uUOgDaYG4iXn2xmkIZTo vv2i5MC9tGzzp523Pj7A4Fod/4idSYy7wPPyZlMIHOLsI2bIjB8jXOVIOdKUc6tnuRpX 9ENIN2JIyk5ExEwXNFQ/fPr5KCz0owCQk4GFuHSWD4CvoaIL7UOF1yq251pvEWUtb9vB RFEMfivMySnH+10MPXomaNbzR4jTOyQ2AqTyaeQcS5OjoxQZahGSUFc1YUIuaga31LoL fiLQ== X-Gm-Message-State: AOAM53398XEXbku6rqLbM2B/ULt5TvRi4RjD/zAZ9rMhKA+7Cuid/efe Yz/dM8tKh/nT4cNGWjHHSD4= X-Google-Smtp-Source: ABdhPJwI6cK8C0iX+ErY9ND7alaFIuttTCXnwe0OjPR0IT7e7pzN+ySKVnVK8N1MdJDe5KUME3Wrmg== X-Received: by 2002:a37:5103:: with SMTP id f3mr3953774qkb.460.1606935704591; Wed, 02 Dec 2020 11:01:44 -0800 (PST) Received: from [192.168.254.67] (h178.165.133.40.static.ip.windstream.net. [40.133.165.178]) by smtp.gmail.com with ESMTPSA id d66sm2761183qke.132.2020.12.02.11.01.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 02 Dec 2020 11:01:44 -0800 (PST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: John Scalia Mime-Version: 1.0 (1.0) Subject: Re: Seeing privileges on a schema Date: Wed, 2 Dec 2020 14:01:42 -0500 Message-Id: <575F6ED5-BDE7-4944-94F0-F32CDC735C15@gmail.com> References: <1668281.1606935611@sss.pgh.pa.us> Cc: pgsql-admin In-Reply-To: <1668281.1606935611@sss.pgh.pa.us> To: Tom Lane X-Mailer: iPad Mail (18B92) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Thanks, I didn=E2=80=99t realize that. Sent from my iPad > On Dec 2, 2020, at 2:00 PM, Tom Lane wrote: >=20 > =EF=BB=BFJohn Scalia writes: >> In psql, I know that \dp or \dpp will show me which privileges are grante= d on tables, views, sequences, and functions, what it doesn=E2=80=99t appear= to be able to do, is show me what privileges are in the schema itself, like= if I grant usage on a schema. Then a \dpp doesn=E2=80=99t produce anything.= Is there an easy way to see what privileges are on a schema? >=20 > \dn+ includes that. >=20 > regards, tom lane