Hey guys,

I think there's a major problem with the 1.2.1 branch.  So far, it
seems to be coming from slonik_init_cluster.  I started with a new
cluster that (almost) worked with 1.2.0, and to make sure it was fresh,
I blew away everything.  slonik_uninstall_nodes, the works.

The new cluster I set up failed pretty much immediately.  I ran the
script slonik_init_cluster generated and node 3 was only entered on
nodes 1 and 3, no paths were stored, and every time I tried to subscribe
a set, the initial table copy never started.  I fixed this by running
slonik_store_node manually for each node, and cutting/pasting the paths
into a file and running it against slony.  Then of course node 3 wasn't
working (node 2 had no record it existed), so I uninstalled it, and used
slonik_store_node to rebuild it.

What on earth is going on here?  Missing node entry?  No paths?  I'm
glad the log switching code is fixed in 1.2.1, but if the initial setup
script doesn't work, I'm a little leery about what else might be wonky
in there.

Confidentiality Note:

The document(s) accompanying this e-mail transmission, if any, and the
e-mail transmittal message containing information from Leapfrog Online
Customer Acquisition, LLC is confidential or privileged. The information
is intended to be for the use of the individual(s) or entity(ies) named
on this e-mail transmission message. If you are not the intended
recipient, be aware that any disclosure, copying, distribution or use of
the contents of this e-mail is prohibited. If you have received this
e-mail in error, please immediately delete this e-mail and notify us by
telephone of the error