> > > If we haven't loaded the .so yet, where would we get the list of
> > > custom GUCs from?
> >
> > This has come up before. We could show the string value of the GUC,
> > if it's been set in postgresql.conf, but we do not have correct
> > values for any of the other columns in pg_settings; nor
On Tue, Jul 02, 2013 at 11:37:13AM -0400, Tom Lane wrote:
> Robert Haas writes:
> > On Tue, Jul 2, 2013 at 9:32 AM, Nikhil Sontakke wrote:
> >> 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 happe
Robert Haas writes:
> On Tue, Jul 2, 2013 at 9:32 AM, Nikhil Sontakke wrote:
>> 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
On Tue, Jul 2, 2013 at 9:32 AM, Nikhil Sontakke 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
Hi,
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 con
