Re: Getting available options - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Getting available options
Date
Msg-id 20080221121513.GA7012@alvh.no-ip.org
Whole thread Raw
In response to Re: Getting available options  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Getting available options  (Magnus Hagander <magnus@hagander.net>)
List 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


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Getting available options
Next
From: Magnus Hagander
Date:
Subject: Re: Getting available options