Hello, Unfortunately I had to do drop node (I used slon function directly) and then recreated again.. I also tryed unsubscribe set, and the subscribe it back, but it did not helped at all..
thx for help Lukas > Lukas wrote: >> Hello, >> >> no, there was no schema changes at all. Postgres logfile does not shows >> anything interesting, 01-24 looks like was power failure, but postgres >> started successfully after that.. >> >> >> One more think, time to time I am getting from slon: >> ERROR remoteListenThread_1: timeout for event selection >> that is only one error, no more errors at all.. >> I am using slon version 1.2.0 >> >> Any ideas? > > L, > > Being less experienced here, I don't have further ideas. I'd probably > use the big hammer of starting over with replication. > > In testing, I did that a number of times with slonik_uninstall_nodes, > which basically resets both databases to a pre-replication state. > > Perhaps someone else will have a more elegant solution. > > Mark > > _______________________________________________ > Slony1-general mailing list > [email protected] > http://gborg.postgresql.org/mailman/listinfo/slony1-general > > -- > This message has been scanned for viruses and > dangerous content, and is believed to be clean. > > -- This message has been scanned for viruses and dangerous content, and is believed to be clean. _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
