On Sat, Jun 22, 2013 at 3:16 PM, Bambi Bellows <bbellows at dotomi.com> wrote:
> LOL.  You guys are killin me.  Meantime, can someone point me to where the log file destination might be hidden?  Because I can't even find out what broke and why.  And as much as it's great to blame my predecessors, they aren't here anymore, and I'm out of my depth on Slony... ob.vi.ous.ly.  And telling my boss to suck it is not really an option for me.
>

I'm not telling you to tell them to suck it, I'm telling you to tell
them you need to fix it right. Take the system offline for as long as
it takes to upgrade postgresql (a few minutes typically). Drop the
current slony, install the latest 2.1.x, and restart replication from
scratch. Running around with your hair on fire at this point isn't
likely to result in a long term sustainable fix, but a slowly
repeating cycle of endless horror as the system gets fixed, breaks,
and gets fixed over and over.