Wed Nov 10 18:21:54 PST 2004
- Previous message: [Slony1-commit] By cbbrowne: Add in some notes on implementation strategy, as well as
- Next message: [Slony1-commit] By cbbrowne: Update schema documentation based on latest comments
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message: ----------- Add a list of features to be worked on Added Files: ----------- slony1-engine: TODO (r1.1) -------------- next part -------------- --- /dev/null +++ TODO @@ -0,0 +1,41 @@ +* Documentation +---------------- + + - Pull material from Chris Browne's wiki + <http://cbbrowne.dyndns.info:8741/cgi-bin/twiki/view/Sandbox/SlonyIAdministration>, + reformat to DocBook, and add this in... + +* Backend +---------------- + +Modify the @NAMESPACE at .logtrigger(namespace, number, keyform) function +so it periodically does a SYNC even if nothing else causes one to be +done. + +This amounts to running some equivalent to the code in sync_thread.c: + + -> Start a serializable transaction + + -> Get last value of sl_action_seq + + -> If value has changed, or sync interval timeout has arrived + + -> Generate SYNC event + select @NAMESPACE at .createEvent('_ at NAMESPACE@', 'SYNC', NULL); + +* slonspool +---------------- + +"Log Spooling" version of slon + +This writes data to files rather than connecting to a destination +database. + +* named nodes +---------------- + +Augment slonik to allow users to give nodes symbolic names that may be +used instead of node numbers throughout Slonik. + +That permits renaming nodes, and using logical names rather than +(likely) cryptic numbers.
- Previous message: [Slony1-commit] By cbbrowne: Add in some notes on implementation strategy, as well as
- Next message: [Slony1-commit] By cbbrowne: Update schema documentation based on latest comments
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list