Steve;

Thanks for your reply.

I will patch slonik_drop_table and slonik_drop_sequence, and wait for your
official update.

Regards;
Michael


On Tue, 15 Nov 2011 22:03:01 -0500
"Steve Singer" <ssinger_pg at sympatico.ca> wrote:

> On Wed, 16 Nov 2011, Michael Cheung wrote:
> 
> > Hi, all;
> >
> > I use pg 8.3.16+slony1 2.1.0 now.
> >
> > I upgrade slony1 from 2.0.2 to 2.1.0 yesterday , anything seems well,
> > but this morning when I do drop table, it retun errors as below.
> 
> This would be a bug introduced in Slony 2.1.0 (that we weren't aware of 
> until now).
> 
> Some of the altperl scripts on an error return -1 but the slonik exit 
> statement was changed to only return values >=0.
> 
> If you change the third line from the bottom in slonik_drop_table script 
> line
> 
> $slonik .= "    exit -1;\n";
> 
> to instead be
> 
> $slonik .= "    exit 1;\n";
> 
> You should avoid that error.  The slonik_drop_sequence script seems to have 
> the same issue.
> 
> I will try to write up a patch later this week.
> 
> >
> > $ ./slonik_drop_table 139 1 | ./slonik
> > <stdin>:12: Error: exitcode was -1 - must be in range [0-255]
> >
> > and I confirm my version is
> > $ ./slonik -v
> > slonik version 2.1.0
> >
> > and I do upgrade as below yesterday,
> > $ ./slonik_update_nodes | ./slonik
> > it complained something like you can't use truncate trigger, but everything
> > seems ok.
> >
> > Any idea about the drop table error?
> >
> > Thanks a lot.
> >
> > Micheal
> >
> > _______________________________________________
> > Slony1-general mailing list
> > Slony1-general at lists.slony.info
> > http://lists.slony.info/mailman/listinfo/slony1-general
> >
>