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/ ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
