What's the point of allow_system_table_mods?

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Subject: What's the point of allow_system_table_mods?
Date: 2019-05-09 14:50:54
Message-ID: 20190509145054.byiwa255xvdbfh3a@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


I'm not quite clear what the goal of allow_system_table_mods
is. Obviously, it's extremely dangerous to target catalogs with DDL. But
at the same time we allow DML to catalog tables without any sort of

I also don't understand what's achieved by having
allow_system_table_mods be PGC_POSTMASTER. If anything it seems to make
it more likely to resort to a) leaving it enabled all the time b) use
DML to modify catalogs.

Wouldn't it be more sensible to disallow all catalog modifications
unless allow_system_table_mods was enabled, and make
allow_system_table_mods PGC_SUSET and GUC_DISALLOW_IN_FILE?


Andres Freund


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-05-09 16:22:39 Re: What's the point of allow_system_table_mods?
Previous Message Andres Freund 2019-05-09 14:43:19 Re: Fuzzy thinking in is_publishable_class