Thu Mar 20 12:19:22 PDT 2014
- Previous message: [Slony1-bugs] [Bug 336] New: Review transaction isolation level requirements for slon database connections.
- Next message: [Slony1-bugs] [Bug 337] Want slon configuration to be available in a table to enable remote access
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=337 Summary: Want slon configuration to be available in a table to enable remote access Product: Slony-I Version: devel Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: low Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: cbbrowne at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 It would be desirable to be able to access the configuration parameters remotely. At present, parameters may exist in the command line or in a slon.conf file loaded using the -f parameter. This does not lend itself to analysis (e.g. - to be able to query nodes in a cluster to figure out how it is configured); the "general method" involves: - Logging onto the machine where the slon is running - Checking "ps" command to get the parameters passed to slon - Consulting a config file indicated by -f parameter, but note that if someone has modified the file since the slon was started, the file may not indicate the present configuration. Note that in confoptions.c, the function set_config_option() includes code to log, at SLON_CONFIG level, all the options that are passed to it; this is used to capture parameters into the Slony log file. This points to a *slightly* better method for looking at slon configuration than was described above; one might instead look in the slon log for the CONFIG entries. The desired enhancement is to add a new table, let's call it sl_slonconf, for now, and to write all the configuration options into that table, at the time a slon starts up. If the table is defined via: create table sl_slonconf ( conf_option text primary key, conf_value text, conf_set_on timestamptz not null default now() ); At slon startup, confoptions.c (or somewhere similar) should prepare a series of SQL statements amounting to... delete from sl_slonconf; insert into sl_slonconf (conf_option, conf_value) values ('vac_frequency', '3'); insert into sl_slonconf (conf_option, conf_value) values ('log_level', '0'); insert into sl_slonconf (conf_option, conf_value) values ('sql_on_connection', ''); ... and so forth... -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 336] New: Review transaction isolation level requirements for slon database connections.
- Next message: [Slony1-bugs] [Bug 337] Want slon configuration to be available in a table to enable remote access
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list