Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 40BF52E0039 for ; Fri, 6 Jun 2008 18:38:46 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 27864-04 for ; Fri, 6 Jun 2008 18:38:37 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from westnet.com (westnet.com [216.187.52.2]) by developer.postgresql.org (Postfix) with ESMTP id 62D862E003F for ; Fri, 6 Jun 2008 18:38:40 -0300 (ADT) Received: from westnet.com (localhost [127.0.0.1]) by westnet.com (8.14.0/8.14.0) with ESMTP id m56Lccsm000819; Fri, 6 Jun 2008 17:38:38 -0400 (EDT) Received: from localhost (gsmith@localhost) by westnet.com (8.14.0/8.13.2/Submit) with ESMTP id m56LccMm000816; Fri, 6 Jun 2008 17:38:38 -0400 (EDT) X-Authentication-Warning: westnet.com: gsmith owned process doing -bs Date: Fri, 6 Jun 2008 17:38:38 -0400 (EDT) From: Greg Smith X-X-Sender: gsmith@westnet.com To: Gregory Stark cc: pgsql-hackers@postgresql.org Subject: Re: Overhauling GUCS In-Reply-To: <87d4muclr6.fsf@oxford.xeocode.com> Message-ID: References: <29525.1212613052@sss.pgh.pa.us> <48472E47.7030701@dunslane.net> <20080605162400.GF16502@alvh.no-ip.org> <48481CBF.6040602@enterprisedb.com> <48481E3A.4010306@hagander.net> <20080605174209.GL16502@alvh.no-ip.org> <20080605212129.GI14498@yugib.highrise.ca> <3F927D52-A0FD-4575-8D24-F0F70C459235@kineticode.com> <4848FAA6.8000903@pse-consulting.de> <87ej7aeuqx.fsf@oxford.xeocode.com> <4849137C.3040008@pse-consulting.de> <877id2erp6.fsf@oxford.xeocode.com> <48492356.4040506@pse-consulting.de> <1618.1212765176@sss.pgh.pa.us> <87d4muclr6.fsf@oxford.xeocode.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/327 X-Sequence-Number: 119440 On Fri, 6 Jun 2008, Gregory Stark wrote: > "Greg Smith" writes: > >> 1) Is it worthwhile to expand the information stored in the GUC structure to >> make it better capable of supporting machine generation and to provide more >> information for tool authors via pg_settings? The exact fields that should or >> shouldn't be included remains controversial; consider "default value", >> "per-session/runtime/restart", and "enum lists" as the list of things that are >> most needed there. > > Isn't that a list of what's *already* there? I should have been clearer there. Some of the items suggested are already in the structure, but aren't visible via pg_settings. In those cases it's just exporting information that's already there. In others (like the suggestion to add a URL to the documentation) it is actually a new field being added as well as its corresponding entry in the settings view. -- * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD