>>> On Wed, Nov 29, 2006 at  2:00 PM, Christopher Browne
<cbbrowne at ca.afilias.info>
wrote:

> Look, the last developer doing serious work on the "altperl" scripts
had
> a change in involvements about a year and a half ago, and has ceased
his
> efforts.

Didn't know that.  In fact, up until you just said something, every
other place I've looked (postgres mailing lists, google searches, etc)
suggested using the altperl stuff.  Then again, one of the things I
noticed was that aside from the paths, slonik_init_cluster actually
allocated the nodes correctly; I would have made the exact same script. 
But when I actually ran the commands against slony was when node 3
failed to register in sl_node with node 2.

But since that's out of the way, I've done a slon_kill and slon_start
to get things going again, and I'm getting tons of errors.  Foreign key
constraint violations (sl_path, sl_subscribe), thread terminations, core
dumps, etc.  I'll recompile with debugging so the backtrace makes at
least some sense other than "bus error."

What's odd is that 1.2.0 worked fine except for the log-switching
problem.

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