Attached is a small page which improves the slonik_build_env "usage"
message a bit.
I wonder if the script is a bit of date, though. It references
@KEYEDTABLES, etc, which don't exist in slon_tools.conf.
A related tool which would be nice might be "slonik_check_env"-- it
would compare the DB against slon_tools.conf and report differences
between the two, perhaps even offering to repair them.
Mark
--- old-slony1-1.2.5/tools/altperl/slonik_build_env.pl 2007-01-08 15:59:09.000000000 -0500
+++ new-slony1-1.2.5/tools/altperl/slonik_build_env.pl 2007-01-08 15:59:09.000000000 -0500
@@ -21,8 +21,9 @@
my @nodes;
my $schema = 'public';
my $usage = "$0 -node host:database:user[:password:port] [-node ...] [-schema myschema]
-First node is assumed to be the master.
-Default schema is \"public\"\n";
+Firsi node is assumed to be the master. Default schema is \"public\"
+
+Queries a database, generating output hopefully suitable for slon_tools.conf\n";
&usage if(!GetOptions('node=s@'=>[EMAIL PROTECTED]));
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
