Re: Clarify "allow_system_table_mods"
От | Adrian Klaver |
---|---|
Тема | Re: Clarify "allow_system_table_mods" |
Дата | |
Msg-id | 41959c84-bfd8-fbe1-6582-0fb1731968f8@aklaver.com обсуждение исходный текст |
Ответ на | Re: Clarify "allow_system_table_mods" (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: Clarify "allow_system_table_mods"
Re: Clarify "allow_system_table_mods" |
Список | pgsql-general |
On 04/25/2016 05:29 PM, Stephen Frost wrote: > * Melvin Davidson (melvin6925@gmail.com) wrote: >> Hmmm, if you go back a few comments, you will note that per initdb --help >> there is no such option available. > > It's not an option *to* initdb, it's an option which is used *by* > initdb. That really did not clear things up:) Does it mean that you can pre-populate the $DATA directory with a postgresql.conf that has allow_system_table_mods set to on and initdb will pick it up? Personally, I think tampering with the system catalogs is foolish. Still if you have documentation for something(even if it is a foot gun) it should be understandable. If the intent is for end users/dba's not use these options I would say take then out of the user docs and put them in the developer Wiki section. > > I'm afraid I'm done with this particular discussion. Hopefully it's > purpose is now clear and you understand a bit better what is required to > actually add a column to pg_class. > > Thanks! > > Stephen > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: