What a read-only Postgres role does and doesn't stop when an AI agent connects
Comments
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Summary
A PostgreSQL 17 test shows that a read-only role, as commonly configured, stops writes, DDL, COPY TO PROGRAM and reads of ungranted tables, but not a session that turns off default_transaction_read_only or statement_timeout itself, or that alters its own stored role defaults.