One of the authors of the patch here. Two reasons:
1. This config option approach was extremely easy to implement
2. Because making this auto.conf read-only would break many existing tools around Postgres that write to auto.conf
1. This config option approach was extremely easy to implement
2. Because making this auto.conf read-only would break many existing tools around Postgres that write to auto.conf
What you really want is to prevent postgres from writing to that file.
That’s more complicated than just making it write only for everyone. Adding an option to stop postgres from doing what you don’t want it to do makes sense to me.