From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
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:15:13 |
Message-ID: | 20080221121513.GA7012@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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).
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2008-02-21 12:22:59 | Re: Getting available options |
Previous Message | manolo.espa | 2008-02-21 11:44:03 | Re: 2WRS [WIP] |