pgsql: Make allow_system_table_mods settable at run time

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Make allow_system_table_mods settable at run time
Date: 2019-11-29 09:24:47
Message-ID: E1iacW7-0003h3-5k@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Make allow_system_table_mods settable at run time

Make allow_system_table_mods settable at run time by superusers. It
was previously postmaster start only.

We don't want to make system catalog DDL wide-open, but there are
occasionally useful things to do like setting reloptions or statistics
on a busy system table, and blocking those doesn't help anyone. Also,
this enables the possibility of writing a test suite for this setting.

Reviewed-by: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Discussion: https://www.postgresql.org/message-id/flat/8b00ea5e-28a7-88ba-e848-21528b632354%402ndquadrant.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/c4a7a392ec8f0ff7701d84768080721ff8a7782e

Modified Files
--------------
doc/src/sgml/config.sgml | 8 +++++---
src/backend/utils/misc/guc.c | 2 +-
2 files changed, 6 insertions(+), 4 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Kapila 2019-11-29 09:54:12 Re: pgsql: Add tests for '-f' option in dropdb utility.
Previous Message Peter Eisentraut 2019-11-29 08:26:30 pgsql: Add error position to an error message