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 <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1l36wi-0001jq-Q0
	for pgsql-admin@arkaria.postgresql.org; Sat, 23 Jan 2021 00:38:32 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1l36wh-0008Io-Ek
	for pgsql-admin@arkaria.postgresql.org; Sat, 23 Jan 2021 00:38:31 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1l36wh-0008If-7J
	for pgsql-admin@lists.postgresql.org; Sat, 23 Jan 2021 00:38:31 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1l36wf-0008FZ-8X
	for pgsql-admin@lists.postgresql.org; Sat, 23 Jan 2021 00:38:30 +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 10N0cOZF1280790;
	Fri, 22 Jan 2021 19:38:24 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
cc: Holger Jakobs <holger@jakobs.com>, pgsql-admin@lists.postgresql.org
Subject: Re: Create Read only user
In-reply-to: 
 <CAOC+FBUmywn6_+E75R3qjs+y=jjpkEP0VKEj9PNaP=YBMw_9Lg@mail.gmail.com>
References: 
 <CALhHtcA5CYQU0SLU673qAdZiixAJJ8GF2ZEJV7YSiq03h5W-jw@mail.gmail.com>
 <87bldgbv9r.fsf@gmail.com> <9e9f3cd6-bd51-29b3-887e-c3af2db91f54@jakobs.com>
 <CAOC+FBUmywn6_+E75R3qjs+y=jjpkEP0VKEj9PNaP=YBMw_9Lg@mail.gmail.com>
Comments: In-reply-to Wells Oliver <wells.oliver@gmail.com>
	message dated "Fri, 22 Jan 2021 16:14:35 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1280788.1611362304.1@sss.pgh.pa.us>
Date: Fri, 22 Jan 2021 19:38:24 -0500
Message-ID: <1280789.1611362304@sss.pgh.pa.us>
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

Wells Oliver <wells.oliver@gmail.com> writes:
> Is there any weird unexpected downside to revoking perms on PUBLIC from all
> my users? It drives me nuts the random stuff that fills this schema up,
> even after I got everyone their own shiny personal schema.

As far as the system is concerned, no; in fact you could drop PUBLIC
altogether if you like.  Your users might whine though...

(Actually, dropping it altogether might be a bad idea, because then
it will come back in your next upgrade.  I think that if you just
change the permissions on it, modern versions of pg_dump/pg_upgrade
will propagate that successfully.)

			regards, tom lane