From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net>, Melvin Davidson <melvin6925(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Clarify "allow_system_table_mods" |
Date: | 2016-04-26 00:41:21 |
Message-ID: | 41959c84-bfd8-fbe1-6582-0fb1731968f8@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/25/2016 05:29 PM, Stephen Frost wrote:
> * Melvin Davidson (melvin6925(at)gmail(dot)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(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | George Neuner | 2016-04-26 01:04:03 | Re: Columnar store as default for PostgreSQL 10? |
Previous Message | Stephen Frost | 2016-04-26 00:29:12 | Re: Clarify "allow_system_table_mods" |