doc/todo: remove old/done items

diff --git a/doc/TODO.txt b/doc/TODO.txt
index 75650e4f62cd4b89253c201020768c45618c6189..353e2943e5ab109bf3a8a7310d5a79e14f4acc47 100644 (file)
--- a/doc/TODO.txt
+++ b/doc/TODO.txt
@@ -12,10 +12,6 @@ Low::
 
 == High Priority ==
 
-* qadmin: register/unregister subconsumer
-  . add syntax
-  . call db-functions.
-
 * londiste takeover: check if all tables exist and are in sync.
   Inform user.  Should the takeover stop if problems?
   How can such state be checked on-the-fly?
@@ -26,9 +22,6 @@ Low::
   - qadmin manpage
   - pgqd manpage
 
-* cascade: merge leaf creation should check if target queue exists -
-  `pgq_node.create_node()` should return error if not.
-
 * cascade takeover: wal failover queue sync.  WAL-failover can be
   behind/ahead from regular replication with partial batch.  Need
   to look up-batched events in wal-slave and full-batches on branches
@@ -50,8 +43,6 @@ Low::
 
 == Medium Priority ==
 
-* Split package (`pgq-modules-X.Y`, `pgqd`, `skytools`) [dimitri]
-
 * tests for things that have not their own regtests
   or are not tested enough during other tests:
   - pgq.RemoteConsumer
@@ -84,8 +75,6 @@ Low::
 
 * dbscript: configurable error timeout (currently it's hardwired to 20s)
 
-* dbscript: `exec_cmd()` needs better name.
-
 * londiste replay: when buffering queries, check their size.  Current
   buffering is by count - flushed if 200 events have been collected.
   That does not take account that some rows can be very large.
@@ -107,20 +96,6 @@ Low::
   Dunno if we can override loggers loaded from skylog.ini.
   Simply redirecting fds 0,1,2 to /dev/null should be enough then.
 
-* londiste add/copy: merge copy without combined queue?  If several
-  partitions need to write data to single place, there are 2 variants:
-  1. Use `--skip-truncate` when adding table in partitons.
-     Problem: it repeatedly drops/creates indexes.
-  2. Use `merge-leaf`->`combined-root` cascading logic, for which
-     Londiste has optimized copy without repeated index dropping+creation.
-     Problem: it expects target combined queue where to copy
-     events and which also triggers the additional copy logic.
-
-  Should there also be 3) - optimized copy without combined queue?
-  Problem: the additional logic needs to checks tables from all the other
-  nodes, all the time, because it has no clear flag that merging
-  needs to happen.  Seems it's better to avoid that.
-
 * londiste: support creating slave from master by pg_dump / PITR.
   Take full dump from root or failover-branch and turn it into
   another branch.