From: stephanhahn <stephan.hahn@muenchen.de>
To: pgsql-admin@postgresql.org
Subject: Re: make postgres readonly
Date: Wed, 3 Mar 2021 07:36:07 -0700 (MST)
Message-ID: <1614782167978-0.post@n3.nabble.com> (raw)
In-Reply-To: <1016718.1614705958@sss.pgh.pa.us>
References: <1614698929965-0.post@n3.nabble.com>
<1016718.1614705958@sss.pgh.pa.us>
Hi Tom, thanks for the reply. I set default_transaction_read_only = on for
the user postgres (seemed to be more practical for me than preventing every
access with pg_hba.conf and create an extra backup user).
Up to now i didn't notice any unwanted effects resulting from this. There
are also still many log entries of the sort 'automatic vacuum of table
"tablename": index scans: 1' (and a few like "@ ERROR: canceling autovacuum
task", which might have other reasons?), so this could suggest a working
autovacuum daemon.
But if you nevertheless think this approach can have any side effects
(because postgres is not only a superuser, but is also used by the DB
system), it seems to be too dangerous for me.
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: stephan.hahn@muenchen.de
Subject: Re: make postgres readonly
In-Reply-To: <1614782167978-0.post@n3.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox