2011/6/16 Luiz K. Matsumura :
> Em 16/06/2011 16:39, Robert Haas escreveu:
>
> 2011/6/10 Luiz K. Matsumura :
>
> I need help to know if the follow scenario is a expected behaviour, a bug of
> postgres or a bug of slony:
>
> Postgres v8.4.8
> Slony-I v 2.0.5
>
> I have table replicated with slony an
Em 16/06/2011 16:39, Robert Haas escreveu:
2011/6/10 Luiz K. Matsumura:
I need help to know if the follow scenario is a expected behaviour, a bug of
postgres or a bug of slony:
Postgres v8.4.8
Slony-I v 2.0.5
I have table replicated with slony and that do some updates in another table
not re
Em 16/06/2011 19:17, Christopher Browne escreveu:
2011/6/10 Luiz K. Matsumura:
Hi,
I need help to know if the follow scenario is a expected behaviour, a bug of
postgres or a bug of slony:
Postgres v8.4.8
Slony-I v 2.0.5
I have table replicated with slony and that do some updates in another t
2011/6/10 Luiz K. Matsumura :
> Hi,
> I need help to know if the follow scenario is a expected behaviour, a bug of
> postgres or a bug of slony:
>
> Postgres v8.4.8
> Slony-I v 2.0.5
>
> I have table replicated with slony and that do some updates in another table
> not replicated.
>
> The trigger o
2011/6/10 Luiz K. Matsumura :
> I need help to know if the follow scenario is a expected behaviour, a bug of
> postgres or a bug of slony:
>
> Postgres v8.4.8
> Slony-I v 2.0.5
>
> I have table replicated with slony and that do some updates in another table
> not replicated.
>
> The trigger on repl
Hi,
I need help to know if the follow scenario is a expected behaviour, a
bug of postgres or a bug of slony:
Postgres v8.4.8
Slony-I v 2.0.5
I have table replicated with slony and that do some updates in another
table not replicated.
The trigger on replicated table was enabled on the slave
