Tue Nov 2 13:16:43 PST 2004
- Previous message: [Slony1-general] When/how does sl_seqlog get cleaned up?
- Next message: [Slony1-general] When/how does sl_seqlog get cleaned up?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 11/2/2004 1:08 AM, Ed L. wrote: > I have a 2-node master-slave replication set up with 1.0.5. It's been > running for a couple days. The sl_seqlog table is now 75MB. Is this > expected? How much larger will it grow? What causes it to get cleaned up? Don't take this wrong, Ed, it is certainly appreciated to point out possible problems with Slony. But maybe you could direct a little bit of the energy, you spend on making sure anybody understands the problem you have with your 200 seldom updated sequences, into studying the code and finding a solution to it that is not disruptive for people with few high frequent accessed sequences. The cleanup is of course done in src/slon/cleanup_thread.c including the vacuuming. Slon never issues a full vacuum, so shrinking of any related tables will only happen ever if you configured a sufficient freespace map and that results in free blocks at the end of the relation for successive vacuum cycles, which happen every 10 minutes. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck at Yahoo.com #
- Previous message: [Slony1-general] When/how does sl_seqlog get cleaned up?
- Next message: [Slony1-general] When/how does sl_seqlog get cleaned up?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list