Greg Sabino Mullane wrote:
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.
Probably so. Seems there is a bit of convergent evolution going on. When I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
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
Folks,
OK, I've checked in my first code module and the configurator project is
officially launched. Come join us at
www.pgfoundry.org/projects/configurator
Further communications will be on the Configurator mailing list only.
from the spec:
What is the Configurator, and Why do We Need It?
Josh Berkus wrote:
Greg,
Not sure how far along you are, but I've been writing some really nifty
extensions to DBD::Pg that allow easy querying of all the current
run-time settings. Could be very useful to this project, seems to me. If
you're interested in possibly using it, let me know, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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?
