X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 035A152812 for ; Wed, 22 Jun 2005 05:31:11 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 56188-08 for ; Wed, 22 Jun 2005 08:31:09 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by svr1.postgresql.org (Postfix) with ESMTP id 122FF52835 for ; Wed, 22 Jun 2005 05:31:08 -0300 (ADT) Received: from p548F2A32.dip0.t-ipconnect.de [84.143.42.50] (helo=pse.dyndns.org) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0ML2Dk-1Dl0dJ2hV8-0000rc; Wed, 22 Jun 2005 10:30:53 +0200 Received: from pse1 ([192.168.0.3]) by pse.dyndns.org with esmtp (Exim 4.44) id 1Dl0dI-0002JZ-9A; Wed, 22 Jun 2005 10:30:52 +0200 Message-ID: <42B921BB.3000705@pse-consulting.de> Date: Wed, 22 Jun 2005 08:30:51 +0000 From: Andreas Pflug User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Greg Sabino Mullane Cc: pgsql-performance@postgresql.org, Josh Berkus Subject: Re: Configurator project launched References: <17c492d2af42972995595f73c426f2aa@biglumber.com> In-Reply-To: <17c492d2af42972995595f73c426f2aa@biglumber.com> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:0ce7ee5c3478b8d72edd8e05ccd40b70 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.041 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200506/426 X-Sequence-Number: 13063 Greg Sabino Mullane wrote: > > >>>>Um, can't we just get that from pg_settings? >>>> >>>>Anyway, I'll be deriving settings from the .conf file, since most of the >>>>time the Configurator will be run on a new installation. >>> >>>Aren't most of the settings all kept in the SHOW variables anyway? > > > As I said, it may not be applicable to this project, but thought I would > offer. One gotcha the module makes transparent is that in older versions of > PG, the variables are returned in a different way (via RAISE). My module > will allow you to get the configuration for any connected database, for > any configuration file, and the defaults for any known version, and do > quick comparisons between them all. So you could use it to see what has > changed between a particular server and its conf file, or the differences > between two conf files, or the differences between two databases, or even show > what has changed in the default conf file from 7.4.7 and 8.0.1. It will also > allow you to rewrite the conf files in a standard way. Sounds a little similar to what's in pgAdmin CVS right now. The configuration editor can retrieve the config file and display configured and active setting concurrently, together with explanations taken from pg_settings (when not run against a pgsql server but a file current settings are missing, comments are taken from a pg_settings csv dump). There's the infrastructure to give hints about all settings, with very few currently implemented. I wonder if this could be combined with the configurator somehow. Currently, integration won't work with Perl, so maybe C for the core and Perl for the interactive part would be better. Regards, Andreas