Wed Jul 11 10:21:33 PDT 2007
- Previous message: [Slony1-commit] slony1-engine/doc/adminguide testbed.sgml
- Next message: [Slony1-commit] slony1-engine TODO
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine In directory main.slony.info:/tmp/cvs-serv14593 Modified Files: TODO Log Message: Revise TODO based on work done and commitments made Index: TODO =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/TODO,v retrieving revision 1.8 retrieving revision 1.9 diff -C2 -d -r1.8 -r1.9 *** TODO 9 Jul 2007 19:34:35 -0000 1.8 --- TODO 11 Jul 2007 17:21:31 -0000 1.9 *************** *** 26,29 **** --- 26,33 ---- generation tools live + - Clone Node - use pg_dump/PITR to populate a new subscriber node + + Jan working on this + Longer Term Items --------------------------- *************** *** 46,63 **** - Windows-compatible version of tools/slony1_dump.sh - - Clone Node - use pg_dump/PITR to populate a new subscriber node - - - test scripts should generate output that can be readily aggregated. - - Initial prototype has them generating SQL output; unfortunately, - if we accept this from arbitrary sources, this is the very picture - of an SQL injection attack. Before doing that, we'll need to - turn it into some suitable tabular/delimited format that can be - parsed into SQL. - - When defining what data there should be, it is useful to use SQL for - now. But this needs NOT to be the form transmitted "across the - wire." - Wishful Thinking ---------------------------- --- 50,53 ----
- Previous message: [Slony1-commit] slony1-engine/doc/adminguide testbed.sgml
- Next message: [Slony1-commit] slony1-engine TODO
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list