From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Getting available options |
Date: | 2008-02-20 22:59:27 |
Message-ID: | 28390.1203548367@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> On Tue, 2008-02-19 at 14:22 +0100, Magnus Hagander wrote:
>> I'd like to add a way for a client (in this case, typicallyi pgadmin,
>> phppgadmin or similar) to get the available options on the server for the
>> GUC settings we have that take fixed options. This is to make it possible
>> to generate pretty dropdown lists of the options.
> How will this work with custom variable classes?
Anything like this will involve an API change in the guc stuff, so
that doesn't seem insurmountable.
I like the idea that was mentioned upthread of creating a new "enum"
category for GUC variables, instead of continuing to abuse the rather
inefficient "string" category for the purpose. One reason is that
we then would not be faced with making an incompatible change in
the arguments of DefineCustomStringVariable.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2008-02-20 23:02:49 | Re: Permanent settings |
Previous Message | Aidan Van Dyk | 2008-02-20 22:53:00 | Re: CVS repository invalid revision |