Operations Manual
Locking Configurations
Security-related configuration settings generally lock themselves for safety reasons. For example, while we can disable [community extensions](#docs:extensions:community_extensions) using the `SET allow_community_extensions = false`, we cannot re-enable them again after the fact without restarting the database. Trying to do so will result in an error:  
```console
Invalid Input Error: Cannot upgrade allow_community_extensions setting while database is running
```  
This prevents untrusted SQL input from re-enabling settings that were explicitly disabled for security reasons.  
Nevertheless, many configuration settings do not disable themselves, such as the resource constraints. If you allow users to run SQL statements unrestricted on your own hardware, it is recommended that you lock the configuration after your own configuration has finished using the following command:  
```sql
SET lock_configuration = true;
```  
This prevents any configuration settings from being modified from that point onwards.