Update of /home/cvsd/slony1/slony1-www
In directory main.slony.info:/tmp/cvs-serv27964

Modified Files:
	Slony 3 Feature Ideas.mm.html 
Log Message:
Draw in items from O/S bugs in Bugzilla, ToDo list


Index: Slony 3 Feature Ideas.mm.html
===================================================================
RCS file: /home/cvsd/slony1/slony1-www/Slony 3 Feature Ideas.mm.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -C 2 -d -r1.5 -r1.6
*** Slony 3 Feature Ideas.mm.html	18 Nov 2010 18:09:41 -0000	1.5
--- Slony 3 Feature Ideas.mm.html	18 Nov 2010 20:52:34 -0000	1.6
***************
*** 107,110 ****
--- 107,123 ----
  </ul>
  </li>
+ <li>SYNC pipelining
+ <ul><li><p>open 2 connections to source DB, start pulling new data while the previous request is pushing I/U/D requests to the subscriber
+ <p>Might be unnecessary if using COPY+triggers to stream data
+ </li>
+ </ul>
+ </li>
+ <li>Compress sequences of DELETE requests
+ <ul><li>Note that TRUNCATE is already replicated
+ 
+ </li>
+ 
+ </ul>
+ </li>
  
  </ul>
***************
*** 117,120 ****
--- 130,136 ----
  
  </li>
+ <li>Untouched since; requires --with-netsnmp option to ./Configure
+ 
+ </li>
  <li>Should we improve it, or drop it?
  
***************
*** 137,155 ****
  </li>
  <li>General Features
! <ul><li>Bug #166: Size of SYNC
! <ul><li>per Steve Singer
  
  </li>
! <li>Useful to ask how much work is involved in particular SYNCs
  
  </li>
! <li>Allows evaluating things like
! <ul><li>Is this SYNC enormous?
  
  </li>
! <li>Is slon busy processing a huge SYNC?
  
  </li>
! <li>Alternatively, if SYNC is small, long running SYNC suggests something broken
  
  </li>
--- 153,180 ----
  </li>
  <li>General Features
! <ul><li>Commit timestamps
! <ul><li>per Jan Wieck
  
  </li>
! <li>Requires PostgreSQL extension
  
  </li>
! <li>Eliminates need for periodic generation of SYNC events
  
  </li>
! <li>Enables carryover of commit times to subscribers
  
  </li>
! 
! </ul>
! </li>
! <li>DDL Triggers
! <ul><li>per Jan Wieck
! 
! </li>
! <li>Requires PostgreSQL extension
! 
! </li>
! <li>Enables automatic generation of DDL_SCRIPT events
  
  </li>
***************
*** 157,174 ****
  </ul>
  </li>
  
  </ul>
  </li>
- <li>Commit timestamps
- <ul><li>per Jan Wieck
  
  </li>
! <li>Requires PostgreSQL extension
  
  </li>
- <li>Eliminates need for periodic generation of SYNC events
  
  </li>
! <li>Enables carryover of commit times to subscribers
  
  </li>
--- 182,220 ----
  </ul>
  </li>
+ <li>pull lexxer from postgres
+ <ul><li>From TODO, probably per Peter Eisentraut
+ 
+ </li>
+ <li>Note that this may be a fair bit more complex than the code in src/parsestatements
+ 
+ </li>
  
  </ul>
  </li>
  
+ </ul>
  </li>
! <li>Bugs Known
! <ul><li>#53 - high RAM usage with high table #
! <ul><li>Likely involves replacing array with hash table
  
  </li>
  
+ </ul>
  </li>
! <li>#80 - slon daemon restarts itself in a loop after failover
! 
! </li>
! <li>#81 - duplicate key sl_nodelock-pkey and duplicate slon(8) processes not detected
! 
! </li>
! <li>#111 - UNSUBSCRIBE SET cancels outstanding SUBSCRIBE SET
! 
! </li>
! <li>#126 - client side KEEPALIVE on connections
! 
! </li>
! <li>#137 - EXECUTE SCRIPT not applied in right order
! <ul><li>Shift DDL from sl_event to sl_log_(1|2)
  
  </li>
***************
*** 176,189 ****
  </ul>
  </li>
! <li>DDL Triggers
! <ul><li>per Jan Wieck
  
  </li>
! <li>Requires PostgreSQL extension
  
  </li>
! <li>Enables automatic generation of DDL_SCRIPT events
  
  </li>
  
  </ul>
--- 222,248 ----
  </ul>
  </li>
! <li>#152 - DDL noisy - might be handled well by "Other Health Criteria" ideas
  
  </li>
! <li>#163 - Change to use TIMESTAMPTZ in Slony-defined tables
  
  </li>
! <li>Bug #166: Size of SYNC
! <ul><li>Useful to ask how much work is involved in particular SYNCs
! 
! </li>
! <li>Allows evaluating things like
! <ul><li>Is this SYNC enormous?
! 
! </li>
! <li>Is slon busy processing a huge SYNC?
  
  </li>
+ <li>Alternatively, if SYNC is small, long running SYNC suggests something broken
+ 
+ </li>
+ 
+ </ul>
+ </li>
  
  </ul>