From: | stephanhahn <stephan(dot)hahn(at)muenchen(dot)de> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: make postgres readonly |
Date: | 2021-03-03 14:36:07 |
Message-ID: | 1614782167978-0.post@n3.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | 2021-03-04 08:40:26 | Different encodings and locales on one machine | |
Previous Message | dbatoCloud Solution | 2021-03-03 11:36:52 | Re: Partition table Creation and Testing using Inherited method |