Re: Getting available options - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Getting available options
Date
Msg-id 200802191456.42476.peter_e@gmx.net
Whole thread Raw
In response to Getting available options  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Getting available options  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Am Dienstag, 19. Februar 2008 schrieb Magnus Hagander:
> 1) Extend pg_settings with a column that contains an array of the available
> options. Extend the config_string GUC struct with a hook that can return
> this data.

Before we get to the interface for reporting this to the client, I wonder how 
we should deal with this in the backend.  Right now, we have string options 
with assign hooks.  You'd need to add a reporting hook or something for each 
parameter.  I'm thinking, perhaps we should invent a new GUC data type enum, 
now that enum is an accepted way to categorize with data around here. :)  
That could simplify the code a bit.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


pgsql-hackers by date:

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