| Type: | bool |
| Default: | off |
| Context: | superuser |
| Restart: | false |
Allows modification of the structure of system tables as well as certain other risky actions on system tables. This is otherwise not allowed even for superusers. Ill-advised use of this setting can cause irretrievable data loss or seriously corrupt the database system. Only superusers can change this setting.
Recommendations
Only available in single-user mode; this setting is for initdb and may be used in the future for upgrade-in-place.
On StackOverflow
- Do system table modifications pass through replication?
- Postgresql doesn't use memory for caching
- Java Hibernate insert hypertable in timescaledb is very slow
- Geoserver WFS + PostgreSQL with large table impossibly slow
- Why does "explain analyzing" this query fnish fast (showing a parallel plan), while running the actual query without "explain analyze" doesn't?
On pgsql-hackers
- Table AM and DROP TABLE [ Was: Table AM and DDLs]
- Support tab completion for upper character inputs in psql
- Re: pgstat_report_activity() and parallel CREATE INDEX (was: Parallel index creation & pg_stat_activity)
- Re: pg13.2: invalid memory alloc request size NNNN
- Re: pg_upgrade fails with non-standard ACL