Tue Jan 27 18:04:39 PST 2009
- Previous message: [Slony1-bugs] [Bug 68] MAKE RPM doesn't work (slony 2.0.0)
- Next message: [Slony1-bugs] NOTICE: Slony-I: log switch to sl_log_1 still in progress - sl_log_2 not truncated
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Folks, I am running Slony 2.0 with Postgres 8.3.4. After doing a series of updates, inserts, and deletes, I am getting the following message in the Slony logs: NOTICE: Slony-I: log switch to sl_log_1 still in progress - sl_log_2 not truncated CONTEXT: PL/pgSQL function "cleanupevent" line 99 at assignment The sl_log_1 and sl_log_2 tables will not truncate and are filled with thousands of rows. The sl_event and sl_confirm tables also have rows that have not been deleted. The data however seems to have replicated from my master to my replicate. Does anyone know what is going on or how to fix this? How does one get the sl_log_1 and sl_log_2 truncating again? I thought the sl_log_1 and sl_log_2 tables were where I would go to find data that had not been replicated yet, but the data in them has been replicated, it just never gets deleted from the Slony log tables. How do you troubleshoot what is causing the stoppage? I have seen numerous posts on this error but no solutions. Thanks in advance!
- Previous message: [Slony1-bugs] [Bug 68] MAKE RPM doesn't work (slony 2.0.0)
- Next message: [Slony1-bugs] NOTICE: Slony-I: log switch to sl_log_1 still in progress - sl_log_2 not truncated
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list