On 13 January 2017 at 13:52, Christopher Browne <cbbrowne at gmail.com> wrote:

> On 13 January 2017 at 08:42, Dave Cramer <davecramer at gmail.com> wrote:
> > Unfortunately bugzilla is down
> > http://www.slony.info/bugzilla/show_bug.cgi?id=111
>
> You can actually get at the bug data...
>
> https://raw.githubusercontent.com/cbbrowne/slony-backups/
> master/Slony-Bugzilla/individual-bugs/111.html
>
> I don't think the problem is too likely to be what's in bug #111, though.
>
> We made a change several versions back to no longer default to Node #1
> as the event node.
>
> I'd expect to see "node -1" being reported on if you have an old
> Slonik script from the "default is 1" days.  These days, you need to
> add an "event node=[some value which *could* be 1]" clause to some of
> the Slonik statements.
>
>
This is a rather old version of slony so I'm sure the bug still exists in
this version.
I'm tempted to do some event surgery fully aware that the patient may not
survive.

That being said can events just be removed ?

Dave Cramer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20170114/60b929d6/attachment.htm