"David G. Johnston" <david.g.johnston@xxxxxxxxx> writes: > On Monday, April 25, 2016, Melvin Davidson <melvin6925@xxxxxxxxx> wrote: >> I need clarification on allow_system_table_mods parameter > If it's going to prevent the action it should be able to do so without > crashing the server..and I doubt it's intended to be opinionated aside from > covering all DDL. What little there is on Google seems to support this. You've got that backwards. Turning allow_system_table_mods on simply disables a bunch of safety/permissions checks, allowing incautious superusers to break their databases by changing system catalog structure. It does not promise to make things work that are incapable of being supported by the underlying C code. For the most part, no change in the rowtype of any system catalog is going to work; the C code has compiled-in notions about the numbers and types of the columns in each catalog. allow_system_table_mods only exists so that initdb can do some setup steps that would otherwise be inconvenient to manage. It's not intended to be used by average mortals; and that's the reason for the lack of documentation, as well as the lack of concern about whether you can crash the system with it. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
