From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Nikhil Sontakke <nikkhils(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Custom gucs visibility |
Date: | 2013-07-02 15:01:39 |
Message-ID: | CA+TgmoZNY-+67Ttrvz_Z54EdXxoRK=t0XR4=oq46vhN=-_AXLQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 2, 2013 at 9:32 AM, Nikhil Sontakke <nikkhils(at)gmail(dot)com> wrote:
> So, if I have a contrib module which adds in a custom guc via
> DefineCustomIntVariable() for example. Now that custom guc is not visible
> via a show command unless that corresponding .so has been loaded into
> memory.
>
> E.g.
>
> postgres=# show pg_buffercache.fancy_custom_guc;
> ERROR: unrecognized configuration parameter
> "pg_buffercache.fancy_custom_guc"
>
> Should we do something about this or we are ok with the current behavior? I
> would prefer to get to see the config parameter value if I so happen to want
> to see it before the load of that contrib module. Thoughts?
If we haven't loaded the .so yet, where would we get the list of
custom GUCs from?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-07-02 15:06:24 | Re: extensible external toast tuple support |
Previous Message | Robert Haas | 2013-07-02 15:00:51 | Re: Large object + FREEZE? |