sarlav kumar sarlavk
Tue Jan 4 22:33:27 PST 2005
Hi All,
 
Thank for all the help everybody. I closed the shells and tried doing the replication again, and it worked. Not sure what was going wrong earlier. 
 
The tables got replicated in the test_slave database.
 
I tried to drop the one of the tables in test_slave database and it actually allowed to drop the table while it was getting replicated!

The Slon process gives the following error message:
 
ERROR  remoteWorkerThread_1: "declare LOG cursor for select     log_origin, log_xid, log_tableid,     log_actionseq, log_cmdtype, log_cmddata from "_test".sl_log_1 where log_origin = 1 and (  order by log_actionseq; " PGRES_FATAL_ERROR ERROR:  syntax error at or near "order" at character 163
ERROR  remoteWorkerThread_1: "close LOG; " PGRES_FATAL_ERROR ERROR:  current transaction is aborted, commands ignored until end of transaction block
ERROR  remoteWorkerThread_1: helper 1 finished with error
ERROR  remoteWorkerThread_1: SYNC aborted

Is this how slony has to react when a replicated table(on the receiving end) is deleted while replication is going on? Would the same thing happen if I delete a table that is providing data, while replication is going on?
 
 While the slon daemons where running, I also tried to add the same set of tables manually in the test_slave DB, but replication does not continue.Why is that the case?
 
If I dont do a pg_dump as shown in the example replication, but manually create the schema for the tables to be replicated on test_slave DB, slon daemon would not replicate the data, Am I right? If this is right, can someone please explain why?
 
 
Thanks a lot!
Saranya Sivakumar
 
 
 
 
 
 

		
---------------------------------
Do you Yahoo!?
 All your favorites on one personal page – Try My Yahoo!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://gborg.postgresql.org/pipermail/slony1-general/attachments/20050104/abff35af/attachment.html


More information about the Slony1-general mailing list