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 1pMN2K-0000cx-Jw for pgsql-general@arkaria.postgresql.org; Mon, 30 Jan 2023 05:49:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pMN2I-0001bS-UK for pgsql-general@arkaria.postgresql.org; Mon, 30 Jan 2023 05:48:58 +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 1pMN2I-0001Wp-It for pgsql-general@lists.postgresql.org; Mon, 30 Jan 2023 05:48:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMN2F-0004rl-Rh for pgsql-general@lists.postgresql.org; Mon, 30 Jan 2023 05:48:58 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 30U5mp0N410288; Mon, 30 Jan 2023 00:48:51 -0500 From: Tom Lane To: "David G. Johnston" cc: =?UTF-8?B?aGlyb3NlIHNoaWdlbyjlu6PngKwg57mB6ZuEIOKWoVNXQ+KXi0FDVCk=?= , "pgsql-general@lists.postgresql.org" Subject: Re: How to control pg_catalog results for each users? In-reply-to: References: <32b68caa-8731-8952-bad5-462566760809@swc.toshiba.co.jp> Comments: In-reply-to "David G. Johnston" message dated "Sun, 29 Jan 2023 22:23:54 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <410286.1675057731.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 30 Jan 2023 00:48:51 -0500 Message-ID: <410287.1675057731@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > On Sunday, January 29, 2023, hirose shigeo(=E5=BB=A3=E7=80=AC =E7=B9=81=E9= =9B=84 =E2=96=A1SWC=E2=97=8BACT) < > shigeo.hirose@toshiba.co.jp> wrote: >> Has there been any discussion or development on controlling this system >> catalog information on a per-user > I found this one: > https://www.postgresql.org/message-id/flat/20160107032927.GT3685%40tamri= el.snowman.net#6d9e59a0d052e7bdccd5a6c4e7a44a3f There have been a ton of discussions around this area over the years. The short answer is that if you think you need to prevent people from seeing the contents of the system catalogs, Postgres is not the database for you. I don't really foresee that changing, because it would break at least as many use-cases as it would enable. The thread David referenced only talks about side-effects on pg_dump, but there are many other applications that would be just as broken if we restricted this. regards, tom lane