diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/skytools3.txt | 33 |
1 files changed, 16 insertions, 17 deletions
diff --git a/doc/skytools3.txt b/doc/skytools3.txt index 70a95f79..0d346e4a 100644 --- a/doc/skytools3.txt +++ b/doc/skytools3.txt @@ -11,9 +11,9 @@ Keep old design from Skytools 2 - No pushing with LISTEN/NOTIFY is used for data transport. - Administrative work happens in separate process. - Can go down anytime, without affecting anything else. -* Relaxed attitude about tables - - Tables can be added/removed any time. - - Inital data sync happens table-by-table, no attempt is made to keep +* Relaxed attitude about tables. + - Tables can be added/removed at any time. + - Initial data sync happens table-by-table, no attempt is made to keep consistent picture between tables during initial copy. New features in Skytools 3 @@ -26,19 +26,19 @@ New features in Skytools 3 - For terminology and technical details see here: set.notes.txt. * New Londiste features: - - Parallel copy - during inital sync several tables can be - copied at the same time. In 2.x the copy already happened in separate - process, making it parallel was just a matter of tuning launching/syncing logic. + - Parallel copy - during initial sync several tables can be copied + at the same time. In 2.x the copy already happened in separate process, + making it parallel was just a matter of tuning launching/syncing logic. - - EXECUTE command, to run random SQL script on all nodes. The script is executed - in single a TX on root, and inserted as an event into the queue in the same TX. - The goal is to emulate DDL AFTER TRIGGER that way. - Londiste itself does no locking and no coordination between nodes. The assumption - is that the DDL commands themselves do enough locking. If more locking is needed - is can be added to script. + - EXECUTE command, to run random SQL script on all nodes. The script is + executed in single TX on root, and inserted as an event into the queue + in the same TX. The goal is to emulate DDL AFTER TRIGGER that way. + Londiste itself does no locking and no coordination between nodes. + The assumption is that the DDL commands themselves do enough locking. + If more locking is needed is can be added to script. - Automatic table or sequence creation by importing the structure - from provider node. Activeted with --create switch for add-table, add-seq. + from provider node. Activated with --create switch for add-table, add-seq. By default *everything* is copied, including Londiste own triggers. The basic idea is that the triggers may be customized and that way we avoid the need to keep track of trigger customizations. @@ -58,8 +58,8 @@ New features in Skytools 3 - Target table can use different name (--dest-table) -* New interactive admin console - qadmin. Because long command lines are not very - user-friendly, this is an experiment on interactive console with +* New interactive admin console - qadmin. Because long command lines are + not very user-friendly, this is an experiment on interactive console with heavy emphasis on tab-completion. * New multi-database ticker: `pgqd`. It is possible to set up one process that @@ -95,7 +95,7 @@ Minor improvements * Skytools 3 modules are parallel installable with Skytools 2. Solved via loader module (like http://faq.pygtk.org/index.py?req=all#2.4[pygtk]). - + import pkgloader pkgloader.require('skytools', '3.0') import skytools @@ -105,4 +105,3 @@ Further reading --------------- * http://skytools.projects.postgresql.org/skytools-3.0/[Documentation] for skytools3. - |