Dnia 2013-07-26, pią o godzinie 09:02 +0200, Robert Wysocki pisze:
> Dnia 2013-07-26, pią o godzinie 07:55 +0200, Robert Wysocki pisze:
> 
> > This probably is what's causing it - especially that we do not replicate
> > this particular sequence - but I wander how is it that it worked (and is
> > still working on prod) with slony <= 2.0.7?
> 
> I've just confirmed it with slony 2.1.3:
> 
> scenario:
> replicated table testseq (id serial, data text), no sequence replication
> 
> test case #1:
> psql> insert into testseq ( data ) values ( 'test' );
> replicated OK, same id on both ends
> 
> test case #2:
> echo "insert into testseq ( data ) values ( 'execute script test' );"
> >/tmp/testsql
> slonik_execute_script 1 /tmp/testsql | slonik
> replication failed, duplicated id error
> 
> test case #3:
> sequence testseq_id_seq added to replication set
> slonik_execute_script 1 /tmp/testsql | slonik
> replicated OK

And now I confirmed that test case #2 works fine (replication OK without
the need to include sequence in replication set) with slony 2.0.4

Regards,
-- 
Robert Wysocki
administrator systemów linuksowych
administrator baz danych
Grupa Unity | ul. Przedmiejska 6-10, 54-201 Wrocław
ul. Conrada 55B, 31-357 Kraków | ul. Złota 59, 00-120 Warszawa