setting up drizzle

PLAN: 

Set up pg_replicator as a reader of the 'transaction' log

phase 1: output to text
phase 2: use libpq to apply statements to pg
phase 3: output as pg protocol (?)

http://www.learningdrizzle.com/?p=53

sudo mkdir -p ~drizzle/drizzle/data
sudo chown -R drizzle ~drizzle/drizzle/data

sudo -u drizzle /usr/local/sbin/drizzled --datadir=/Users/drizzle/drizzle/data --default-replicator-enable=true --transaction_log_enable=true &

=====

error: 
selena@lulu:trunk #533 16:33 :) sudo -u drizzle /usr/local/sbin/drizzled --datadir=~drizzle/drizzle/data
Data directory /usr/local/~drizzle/drizzle/data/ does not exist
Aborting
/usr/local/sbin/drizzled: Shutdown complete
* does't catch ctl-C, or ctl-Z :D
* Doesn't interpret '~'

## Turn on replication

default-replicator-enable

http://drizzle.org/wiki/Replication

http://www.jpipes.com/index.php?/archives/290-Towards-a-New-Modular-Replication-Architecture.html

Padraig:
http://posulliv.github.com/2009/07/24/developing-a-replicator-plugin-for-drizzle.html

Jay's docs:
http://www.jpipes.com/index.php?/archives/302-Drizzle-Replication-Changes-in-API-to-support-Group-Commit.html
http://www.jpipes.com/index.php?/archives/299-Drizzle-Replication-The-Transaction-Log.html

Replication has been redesigned to use Google's ProtoBuffer library as a message format. This makes it simple to write new replication clients. Currently replication plans include plugins to write to a file and to send messages to a Gearman server. The internals of replication now work on tuple changes, thus removing any deterministic behavior requirements.

*[http://www.jpipes.com/index.php?/archives/290-Towards-a-New-Modular-Replication-Architecture.html Replication Architecture]
*[http://jpipes.com/index.php?/archives/298-Drizzle-Replication-The-Command-Message.html The Command Message]
*[http://posulliv.github.com/2009/07/24/developing-a-replicator-plugin-for-drizzle.html Developing a Replication Plugin]
*[http://www.jpipes.com/index.php?/archives/302-Drizzle-Replication-Changes-in-API-to-support-Group-Commit.html Group Commit]
*[http://jpipes.com/index.php?/archives/299-Drizzle-Replication-The-Transaction-Log.html Transaction Log]
*[http://blogs.sun.com/elambert/entry/the_gearman_replicator_for_drizzle Gearman replicator for Drizzle]
*[http://scale-out-blog.blogspot.com/2009/10/replicating-from-mysql-to-drizzle-and.html Replicating from MySQL to Drizzle and beyond]
*[http://developian.blogspot.com/2009/10/replication-from-mysql-to-drizzle-using.html Replicating from MySQL to Drizzle using Tungsten Replicator]

http://mysqlmusings.blogspot.com/2008/08/using-protobuf-for-designing-and.html