Fri Apr 11 07:56:10 PDT 2008
- Previous message: [Slony1-commit] slony1-engine/doc/adminguide cluster.sgml faq.sgml slonik_ref.sgml
- Next message: [Slony1-commit] slony1-engine/src/backend slony1_funcs.sql
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine In directory main.slony.info:/tmp/cvs-serv13243 Modified Files: TODO Log Message: Add in TODO item to have tuple application take place on the subscriber via running triggers on log tables, and loading the data in via COPY Index: TODO =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/TODO,v retrieving revision 1.15 retrieving revision 1.16 diff -C2 -d -r1.15 -r1.16 *** TODO 22 Nov 2007 23:02:06 -0000 1.15 --- TODO 11 Apr 2008 14:56:08 -0000 1.16 *************** *** 116,127 **** - Could it have some policy in it as to preferred failover targets? - - Have Tuple Application Work take place on the subscriber - - - When data is pulled from sl_log_*, turn the output into a COPY - statement - - - Thus, the data is input, in bulk, using a COPY statement - - - Then have triggers on sl_log_* that perform the "distribution" - work to insert/delete/update data on the subscriber --- 116,117 ----
- Previous message: [Slony1-commit] slony1-engine/doc/adminguide cluster.sgml faq.sgml slonik_ref.sgml
- Next message: [Slony1-commit] slony1-engine/src/backend slony1_funcs.sql
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list