From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Why don't custom GUCs show in pg_settings? |
Date: | 2016-04-30 16:39:07 |
Message-ID: | 20763.1462034347@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> I've seen and can work with various work-arounds but it seems odd that
> pg_settings doesn't show these custom GUCs.
Because we don't know what type they should be.
If we're ever to support custom GUCs properly, rather than as a hack that
accidentally sorta works, there needs to be a way to declare them and
establish their properties; whereupon there would be info for pg_settings
to display.
> Is there a simple way to read the value without receiving an error if the
> value is missing?
See 10fb48d66, which I don't particularly approve of because it piled
another hack on top of that mess without doing a thing to make it cleaner.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2016-04-30 17:01:44 | Re: Why don't custom GUCs show in pg_settings? |
Previous Message | David G. Johnston | 2016-04-30 16:22:52 | Why don't custom GUCs show in pg_settings? |