From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Getting available options |
Date: | 2008-02-21 12:22:59 |
Message-ID: | 20080221122259.GZ8138@svr2.hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 21, 2008 at 09:15:13AM -0300, Alvaro Herrera wrote:
> Magnus Hagander wrote:
>
> > > 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.
> >
> > Yeah, I liked that one as well - I'm going to look at doing that, and will
> > present some code as soon as I can to discuss the exact implementation. I
> > don't think it'll be too much work.
>
> It seems we have two clear proposal that had clear acceptance, and for
> which we now need code: this enum stuff is one, and the other one is
> the addition of "file origin" to pg_settings so that you can tell
> what file a setting comes from (i.e. postgresql.conf or an included
> file).
Yes. And IMHO those are required befoer we can implement the stuff about
writing configuration variables in a good way. So they're now both high up
on my TODO list. If anybody wants to work on them, please talk to me first
so we don't dulpicate effort :-)
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2008-02-21 14:23:23 | Re: Timezone view |
Previous Message | Alvaro Herrera | 2008-02-21 12:15:13 | Re: Getting available options |