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 1lH8mc-0007EC-QM for pgsql-admin@arkaria.postgresql.org; Tue, 02 Mar 2021 17:26:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lH8mb-0005uz-P2 for pgsql-admin@arkaria.postgresql.org; Tue, 02 Mar 2021 17:26:05 +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 1lH8mb-0005ur-HH for pgsql-admin@lists.postgresql.org; Tue, 02 Mar 2021 17:26:05 +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 1lH8mZ-0002Ye-GN for pgsql-admin@postgresql.org; Tue, 02 Mar 2021 17:26:05 +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 122HPwvK1016719; Tue, 2 Mar 2021 12:25:59 -0500 From: Tom Lane To: Stephan Hahn cc: pgsql-admin@postgresql.org Subject: Re: make postgres readonly In-reply-to: <1614698929965-0.post@n3.nabble.com> References: <1614698929965-0.post@n3.nabble.com> Comments: In-reply-to Stephan Hahn message dated "Tue, 02 Mar 2021 08:28:49 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1016717.1614705958.1@sss.pgh.pa.us> Date: Tue, 02 Mar 2021 12:25:58 -0500 Message-ID: <1016718.1614705958@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Stephan Hahn writes: > Does it cause any problems if i set the user postgres to readonly? Not really sure what you have in mind there, but superusers bypass all permissions checks. Even if it worked, it'd be likely to break the autovacuum daemon. regards, tom lane